Generating copies through interoperability between a data storage management system and appliances for data storage and deduplication

ABSTRACT

Illustrative storage manager and media agent are enhanced to interoperate with deduplication appliances. Advantages are realized when making secondary and tertiary copies and also when restoring from a deduplication appliance. Tiered indexing minimizes how much data is retained and stored at media agents. Tiered indexing enables media agents to efficiently extract needed information from deduplication appliances to make tertiary copies and to restore backed up copies. Interoperability techniques include media agents generating separate data streams to the deduplication appliance. Each data stream carries a different kind of data, e.g., payload data, metadata content, or high-level index information. On initial backup, the media agent instructs the deduplication appliance to deduplicate the payload data stream but not the other data streams, thus intelligently applying resources to data most likely to benefit from deduplication. For tertiary copies (copies of pre-existing copies at the deduplication appliance), the media agent avoids handling payload data altogether.

INCORPORATION BY REFERENCE TO ANY PRIORITY APPLICATIONS

This application is a Continuation of U.S. patent application Ser. No.16/201,897 filed on Nov. 27, 2018. Any and all applications for which aforeign or domestic priority claim is identified in the Application DataSheet of the present application are hereby incorporated by reference intheir entireties under 37 CFR 1.57.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentand/or the patent disclosure as it appears in the United States Patentand Trademark Office patent file and/or records, but otherwise reservesall copyrights whatsoever.

BACKGROUND

Businesses recognize the commercial value of their data and seekreliable, cost-effective ways to protect the information stored on theircomputer networks while minimizing impact on productivity. A companymight back up critical computing systems such as databases, fileservers, web servers, virtual machines, and so on as part of a daily,weekly, or monthly maintenance schedule. The company may similarlyprotect computing systems used by its employees, such as those used byan accounting department, marketing department, engineering department,and so forth.

SUMMARY

Traditional data storage management systems place substantial dataprocessing loads upon key components that process and prepare copies forsecondary storage. Appliances have emerged that natively performefficient storage techniques, such as compression, deduplication, etc.

The present inventors devised a number of interoperability techniquesbetween certain components of a data storage management system andappliances with data storage and deduplication capabilities (hereinafter“deduplication appliances”). Illustrative data storage managementcomponents such as storage manager, media agent, and media agent indexare enhanced to interoperate with deduplication appliances. Illustrativeadvantages are realized in several scenarios, including when makinginitial secondary copies, when making tertiary copies (i.e., copies ofcopies), and also when restoring backed up data from a deduplicationappliance.

The illustrative embodiments feature a tiered indexing approach thatminimizes how much data is retained and stored at media agents. Thetiered indexing enables media agents to efficiently extract neededinformation from the example deduplication appliance in order to maketertiary copies and to restore backed up copies.

The illustrative storage manager and media agents rely on thededuplication appliance to handle deduplication, storage, and trackingof data stored therein, while retaining indexing and tracking strengthsdesigned into the illustrative data storage management system.Interoperability techniques include the media agent generating separatespecial-purpose data streams transmitted to the deduplication appliance.Each special-purpose data stream carries a different kind of data, e.g.,payload data, metadata content, or high-level index information. Oninitial backup, the illustrative media agent instructs the deduplicationappliance to deduplicate the payload data stream but not the other datastreams, thus intelligently applying resources to data that is mostlikely to benefit from deduplication. The illustrative media agent alsoretains useful index information and metadata content from the backed upcopies that it uses autonomously without the deduplication appliance,e.g., for reporting, browsing, etc.

When tertiary copies are created, i.e., copies made from pre-existingcopies that are already stored at the deduplication appliance, the mediaagent avoids handling payload data. No payload data passes through orplays back at the illustrative media agent in tertiary copy operations,e.g., synthetic-full copies, auxiliary copies, etc. Instead, theillustrative media agent uses tiered indexing to instruct thededuplication appliance to find and handle the payload data directly. Onrestore, the deduplication appliance takes care of rehydratingdeduplicated data using its own native capabilities, so that thereceiving media agent has a relatively light data processing load tofinish restoring the data.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a block diagram illustrating an exemplary informationmanagement system.

FIG. 1B is a detailed view of a primary storage device, a secondarystorage device, and some examples of primary data and secondary copydata.

FIG. 1C is a block diagram of an exemplary information management systemincluding a storage manager, one or more data agents, and one or moremedia agents.

FIG. 1D is a block diagram illustrating a scalable informationmanagement system.

FIG. 1E illustrates certain secondary copy operations according to anexemplary storage policy.

FIGS. 1F-1H are block diagrams illustrating suitable data structuresthat may be employed by the information management system.

FIG. 2A illustrates a system and technique for synchronizing primarydata to a destination such as a failover site using secondary copy data.

FIG. 2B illustrates an information management system architectureincorporating use of a network file system (NFS) protocol forcommunicating between the primary and secondary storage subsystems.

FIG. 2C is a block diagram of an example of a highly scalable manageddata pool architecture.

FIG. 3A depicts a data storage management system 300 forinteroperability between storage management components and one or moreappliances for data storage and deduplication (“deduplicationappliance”), according to an illustrative embodiment of the presentinvention.

FIG. 3B depicts some details of system 300 including a clientconfiguration and media agent connectivity to a deduplication appliance.

FIG. 4 depicts a high level view of illustrative logic used by anexample deduplication appliance.

FIG. 5A depicts a logical view of a backup operation in system 300 forgenerating secondary copies based on primary data by segregatingpayload, metadata, and index into separate data streams transmitted toan example deduplication appliance.

FIG. 5B depicts some details of data streams 510, 520, and 530 forgenerating secondary copies to be stored in an example deduplicationappliance.

FIG. 6 depicts a logical view of a backup operation in system 300 forgenerating tertiary copies based on a combination of other copies, e.g.,making a synthetic-full copy stored to an example deduplicationappliance.

FIG. 7 depicts a logical view of a backup operation in system 300 forgenerating tertiary copies based on other copies, e.g., making anauxiliary copy stored to an example deduplication appliance.

FIG. 8 depicts a logical view of a backup operation in system 300 forgenerating tertiary copies based on other copies, e.g., making anauxiliary copy from a first deduplication appliance to a seconddeduplication appliance.

FIG. 9 depicts a logical view of a recovery operation in system 300 forrestoring primary data from secondary/tertiary copies stored in anexample deduplication appliance.

FIG. 10 depicts a method 1000 in system 300 for generating secondarycopies based on primary data by segregating payload, metadata, and indexinto separate data streams, according to an illustrative embodiment ofthe present invention.

FIG. 11 depicts some salient operations in block 1004 of method 1000.

FIG. 12 depicts a method 1200 in system 300 for generating tertiarycopies based on other copies, according to an illustrative embodiment ofthe present invention.

FIG. 13 depicts a method 1300 in system 300 for restoring primary datafrom secondary/tertiary copies stored in an example deduplicationappliance, according to an illustrative embodiment of the presentinvention.

DETAILED DESCRIPTION

Detailed descriptions and examples of systems and methods according toone or more illustrative embodiments of the present invention may befound in the section entitled INTEROPERABILITY BETWEEN COMPONENTS OF ADATA STORAGE MANAGEMENT SYSTEM AND APPLIANCES FOR DATA STORAGE ANDDEDUPLICATION, as well as in the section entitled Example Embodiments,and also in FIGS. 3A-13 herein. Furthermore, components andfunctionality for interoperability between components of a data storagemanagement system and appliances for data storage and deduplication maybe configured and/or incorporated into information management systemssuch as those described herein in FIGS. 1A-1H and 2A-2C.

Various embodiments described herein are intimately tied to, enabled by,and would not exist except for, computer technology. For example,generating data chunks and segregating different types of data chunks todifferent data streams transmitted to an example deduplication appliancedescribed herein in reference to various embodiments cannot reasonablybe performed by humans alone, without the computer technology upon whichthey are implemented.

Information Management System Overview

With the increasing importance of protecting and leveraging data,organizations simply cannot risk losing critical data. Moreover, runawaydata growth and other modern realities make protecting and managing dataincreasingly difficult. There is therefore a need for efficient,powerful, and user-friendly solutions for protecting and managing dataand for smart and efficient management of data storage. Depending on thesize of the organization, there may be many data production sourceswhich are under the purview of tens, hundreds, or even thousands ofindividuals. In the past, individuals were sometimes responsible formanaging and protecting their own data, and a patchwork of hardware andsoftware point solutions may have been used in any given organization.These solutions were often provided by different vendors and had limitedor no interoperability. Certain embodiments described herein addressthese and other shortcomings of prior approaches by implementingscalable, unified, organization-wide information management, includingdata storage management.

FIG. 1A shows one such information management system 100 (or “system100”), which generally includes combinations of hardware and softwareconfigured to protect and manage data and metadata that are generatedand used by computing devices in system 100. System 100 may be referredto in some embodiments as a “storage management system” or a “datastorage management system.” System 100 performs information managementoperations, some of which may be referred to as “storage operations” or“data storage operations,” to protect and manage the data residing inand/or managed by system 100. The organization that employs system 100may be a corporation or other business entity, non-profit organization,educational institution, household, governmental agency, or the like.

Generally, the systems and associated components described herein may becompatible with and/or provide some or all of the functionality of thesystems and corresponding components described in one or more of thefollowing U.S. patents/publications and patent applications assigned toCommvault Systems, Inc., each of which is hereby incorporated byreference in its entirety herein:

-   -   U.S. Pat. No. 7,035,880, entitled “Modular Backup and Retrieval        System Used in Conjunction With a Storage Area Network”;    -   U.S. Pat. No. 7,107,298, entitled “System And Method For        Archiving Objects In An Information Store”;    -   U.S. Pat. No. 7,246,207, entitled “System and Method for        Dynamically Performing Storage Operations in a Computer        Network”;    -   U.S. Pat. No. 7,315,923, entitled “System And Method For        Combining Data Streams In Pipelined Storage Operations In A        Storage Network”;    -   U.S. Pat. No. 7,343,453, entitled “Hierarchical Systems and        Methods for Providing a Unified View of Storage Information”;    -   U.S. Pat. No. 7,395,282, entitled “Hierarchical Backup and        Retrieval System”;    -   U.S. Pat. No. 7,529,782, entitled “System and Methods for        Performing a Snapshot and for Restoring Data”;    -   U.S. Pat. No. 7,617,262, entitled “System and Methods for        Monitoring Application Data in a Data Replication System”;    -   U.S. Pat. No. 7,734,669, entitled “Managing Copies Of Data”;    -   U.S. Pat. No. 7,747,579, entitled “Metabase for Facilitating        Data Classification”;    -   U.S. Pat. No. 8,156,086, entitled “Systems And Methods For        Stored Data Verification”;    -   U.S. Pat. No. 8,170,995, entitled “Method and System for Offline        Indexing of Content and Classifying Stored Data”;    -   U.S. Pat. No. 8,230,195, entitled “System And Method For        Performing Auxiliary Storage Operations”;    -   U.S. Pat. No. 8,285,681, entitled “Data Object Store and Server        for a Cloud Storage Environment, Including Data Deduplication        and Data Management Across Multiple Cloud Storage Sites”;    -   U.S. Pat. No. 8,307,177, entitled “Systems And Methods For        Management Of Virtualization Data”;    -   U.S. Pat. No. 8,364,652, entitled “Content-Aligned, Block-Based        Deduplication”;    -   U.S. Pat. No. 8,578,120, entitled “Block-Level Single        Instancing”;    -   U.S. Pat. No. 8,954,446, entitled “Client-Side Repository in a        Networked Deduplicated Storage System”;    -   U.S. Pat. No. 9,020,900, entitled “Distributed Deduplicated        Storage System”;    -   U.S. Pat. No. 9,098,495, entitled “Application-Aware and Remote        Single Instance Data Management”;    -   U.S. Pat. No. 9,239,687, entitled “Systems and Methods for        Retaining and Using Data Block Signatures in Data Protection        Operations”;    -   U.S. Pat. No. 9,633,033, entitled “High Availability Distributed        Deduplicated Storage System”;    -   U.S. Pat. No. 9,904,598, entitled “Content-Independent and        Database Management System-Independent Synthetic Full Backup of        a Database based on Snapshot Technology”;    -   U.S. Pat. Pub. No. 2006/0224846, entitled “System and Method to        Support Single Instance Storage Operations”;    -   U.S. Pat. Pub. No. 2016-0350391, entitled “Replication Using        Deduplicated Secondary Copy Data”;    -   U.S. Pat. Pub. No. 2017-0168903 A1, entitled “Live        Synchronization and Management of Virtual Machines across        Computing and Virtualization Platforms and Using Live        Synchronization to Support Disaster Recovery”;    -   U.S. Pat. Pub. No. 2017-0185488 A1, entitled “Application-Level        Live Synchronization Across Computing Platforms Including        Synchronizing Co-Resident Applications To Disparate Standby        Destinations And Selectively Synchronizing Some Applications And        Not Others”;    -   U.S. Pat. Pub. No. 2017-0192866 A1, entitled “System For        Redirecting Requests After A Secondary Storage Computing Device        Failure”;    -   U.S. Pat. Pub. No. 2017-0235647 A1, entitled “Data Protection        Operations Based on Network Path Information”; and    -   U.S. Pat. Pub. No. 2017-0242871 A1, entitled “Data Restoration        Operations Based on Network Path Information”.

System 100 includes computing devices and computing technologies. Forinstance, system 100 can include one or more client computing devices102 and secondary storage computing devices 106, as well as storagemanager 140 or a host computing device for it. Computing devices caninclude, without limitation, one or more: workstations, personalcomputers, desktop computers, or other types of generally fixedcomputing systems such as mainframe computers, servers, andminicomputers. Other computing devices can include mobile or portablecomputing devices, such as one or more laptops, tablet computers,personal data assistants, mobile phones (such as smartphones), and othermobile or portable computing devices such as embedded computers, set topboxes, vehicle-mounted devices, wearable computers, etc. Servers caninclude mail servers, file servers, database servers, virtual machineservers, and web servers. Any given computing device comprises one ormore processors (e.g., CPU and/or single-core or multi-core processors),as well as corresponding non-transitory computer memory (e.g.,random-access memory (RAM)) for storing computer programs which are tobe executed by the one or more processors. Other computer memory formass storage of data may be packaged/configured with the computingdevice (e.g., an internal hard disk) and/or may be external andaccessible by the computing device (e.g., network-attached storage, astorage array, etc.). In some cases, a computing device includes cloudcomputing resources, which may be implemented as virtual machines. Forinstance, one or more virtual machines may be provided to theorganization by a third-party cloud service vendor.

In some embodiments, computing devices can include one or more virtualmachine(s) running on a physical host computing device (or “hostmachine”) operated by the organization. As one example, the organizationmay use one virtual machine as a database server and another virtualmachine as a mail server, both virtual machines operating on the samehost machine. A Virtual machine (“VM”) is a software implementation of acomputer that does not physically exist and is instead instantiated inan operating system of a physical computer (or host machine) to enableapplications to execute within the VM's environment, i.e., a VM emulatesa physical computer. AVM includes an operating system and associatedvirtual resources, such as computer memory and processor(s). Ahypervisor operates between the VM and the hardware of the physical hostmachine and is generally responsible for creating and running the VMs.Hypervisors are also known in the art as virtual machine monitors or avirtual machine managers or “VMMs”, and may be implemented in software,firmware, and/or specialized hardware installed on the host machine.Examples of hypervisors include ESX Server, by VMware, Inc. of PaloAlto, Calif.; Microsoft Virtual Server and Microsoft Windows ServerHyper-V, both by Microsoft Corporation of Redmond, Wash.; Sun xVM byOracle America Inc. of Santa Clara, Calif.; and Xen by Citrix Systems,Santa Clara, Calif. The hypervisor provides resources to each virtualoperating system such as a virtual processor, virtual memory, a virtualnetwork device, and a virtual disk. Each virtual machine has one or moreassociated virtual disks. The hypervisor typically stores the data ofvirtual disks in files on the file system of the physical host machine,called virtual machine disk files (“VMDK” in VMware lingo) or virtualhard disk image files (in Microsoft lingo). For example, VMware's ESXServer provides the Virtual Machine File System (VMFS) for the storageof virtual machine disk files. A virtual machine reads data from andwrites data to its virtual disk much the way that a physical machinereads data from and writes data to a physical disk. Examples oftechniques for implementing information management in a cloud computingenvironment are described in U.S. Pat. No. 8,285,681. Examples oftechniques for implementing information management in a virtualizedcomputing environment are described in U.S. Pat. No. 8,307,177.

Information management system 100 can also include electronic datastorage devices, generally used for mass storage of data, including,e.g., primary storage devices 104 and secondary storage devices 108.Storage devices can generally be of any suitable type including, withoutlimitation, disk drives, storage arrays (e.g., storage-area network(SAN) and/or network-attached storage (NAS) technology), semiconductormemory (e.g., solid state storage devices), network attached storage(NAS) devices, tape libraries, or other magnetic, non-tape storagedevices, optical media storage devices, combinations of the same, etc.In some embodiments, storage devices form part of a distributed filesystem. In some cases, storage devices are provided in a cloud storageenvironment (e.g., a private cloud or one operated by a third-partyvendor), whether for primary data or secondary copies or both.

Depending on context, the term “information management system” can referto generally all of the illustrated hardware and software components inFIG. 1C, or the term may refer to only a subset of the illustratedcomponents. For instance, in some cases, system 100 generally refers toa combination of specialized components used to protect, move, manage,manipulate, analyze, and/or process data and metadata generated byclient computing devices 102. However, system 100 in some cases does notinclude the underlying components that generate and/or store primarydata 112, such as the client computing devices 102 themselves, and theprimary storage devices 104. Likewise secondary storage devices 108(e.g., a third-party provided cloud storage environment) may not be partof system 100. As an example, “information management system” or“storage management system” may sometimes refer to one or more of thefollowing components, which will be described in further detail below:storage manager, data agent, and media agent.

One or more client computing devices 102 may be part of system 100, eachclient computing device 102 having an operating system and at least oneapplication 110 and one or more accompanying data agents executingthereon; and associated with one or more primary storage devices 104storing primary data 112. Client computing device(s) 102 and primarystorage devices 104 may generally be referred to in some cases asprimary storage subsystem 117.

Client Computing Devices, Clients, and Subclients

Typically, a variety of sources in an organization produce data to beprotected and managed. As just one illustrative example, in a corporateenvironment such data sources can be employee workstations and companyservers such as a mail server, a web server, a database server, atransaction server, or the like. In system 100, data generation sourcesinclude one or more client computing devices 102. A computing devicethat has a data agent 142 installed and operating on it is generallyreferred to as a “client computing device” 102, and may include any typeof computing device, without limitation. A client computing device 102may be associated with one or more users and/or user accounts.

A “client” is a logical component of information management system 100,which may represent a logical grouping of one or more data agentsinstalled on a client computing device 102. Storage manager 140recognizes a client as a component of system 100, and in someembodiments, may automatically create a client component the first timea data agent 142 is installed on a client computing device 102. Becausedata generated by executable component(s) 110 is tracked by theassociated data agent 142 so that it may be properly protected in system100, a client may be said to generate data and to store the generateddata to primary storage, such as primary storage device 104. However,the terms “client” and “client computing device” as used herein do notimply that a client computing device 102 is necessarily configured inthe client/server sense relative to another computing device such as amail server, or that a client computing device 102 cannot be a server inits own right. As just a few examples, a client computing device 102 canbe and/or include mail servers, file servers, database servers, virtualmachine servers, and/or web servers.

Each client computing device 102 may have application(s) 110 executingthereon which generate and manipulate the data that is to be protectedfrom loss and managed in system 100. Applications 110 generallyfacilitate the operations of an organization, and can include, withoutlimitation, mail server applications (e.g., Microsoft Exchange Server),file system applications, mail client applications (e.g., MicrosoftExchange Client), database applications or database management systems(e.g., SQL, Oracle, SAP, Lotus Notes Database), word processingapplications (e.g., Microsoft Word), spreadsheet applications, financialapplications, presentation applications, graphics and/or videoapplications, browser applications, mobile applications, entertainmentapplications, and so on. Each application 110 may be accompanied by anapplication-specific data agent 142, though not all data agents 142 areapplication-specific or associated with only application. A file managerapplication, e.g., Microsoft Windows Explorer, may be considered anapplication 110 and may be accompanied by its own data agent 142. Clientcomputing devices 102 can have at least one operating system (e.g.,Microsoft Windows, Mac OS X, iOS, IBM z/OS, Linux, other Unix-basedoperating systems, etc.) installed thereon, which may support or hostone or more file systems and other applications 110. In someembodiments, a virtual machine that executes on a host client computingdevice 102 may be considered an application 110 and may be accompaniedby a specific data agent 142 (e.g., virtual server data agent).

Client computing devices 102 and other components in system 100 can beconnected to one another via one or more electronic communicationpathways 114. For example, a first communication pathway 114 maycommunicatively couple client computing device 102 and secondary storagecomputing device 106; a second communication pathway 114 maycommunicatively couple storage manager 140 and client computing device102; and a third communication pathway 114 may communicatively couplestorage manager 140 and secondary storage computing device 106, etc.(see, e.g., FIG. 1A and FIG. 1C). A communication pathway 114 caninclude one or more networks or other connection types including one ormore of the following, without limitation: the Internet, a wide areanetwork (WAN), a local area network (LAN), a Storage Area Network (SAN),a Fibre Channel (FC) connection, a Small Computer System Interface(SCSI) connection, a virtual private network (VPN), a token ring orTCP/IP based network, an intranet network, a point-to-point link, acellular network, a wireless data transmission system, a two-way cablesystem, an interactive kiosk network, a satellite network, a broadbandnetwork, a baseband network, a neural network, a mesh network, an ad hocnetwork, other appropriate computer or telecommunications networks,combinations of the same or the like. Communication pathways 114 in somecases may also include application programming interfaces (APIs)including, e.g., cloud service provider APIs, virtual machine managementAPIs, and hosted service provider APIs. The underlying infrastructure ofcommunication pathways 114 may be wired and/or wireless, analog and/ordigital, or any combination thereof; and the facilities used may beprivate, public, third-party provided, or any combination thereof,without limitation.

A “subclient” is a logical grouping of all or part of a client's primarydata 112. In general, a subclient may be defined according to how thesubclient data is to be protected as a unit in system 100. For example,a subclient may be associated with a certain storage policy. A givenclient may thus comprise several subclients, each subclient associatedwith a different storage policy. For example, some files may form afirst subclient that requires compression and deduplication and isassociated with a first storage policy. Other files of the client mayform a second subclient that requires a different retention schedule aswell as encryption, and may be associated with a different, secondstorage policy. As a result, though the primary data may be generated bythe same application 110 and may belong to one given client, portions ofthe data may be assigned to different subclients for distinct treatmentby system 100. More detail on subclients is given in regard to storagepolicies below.

Primary Data and Exemplary Primary Storage Devices

Primary data 112 is generally production data or “live” data generatedby the operating system and/or applications 110 executing on clientcomputing device 102. Primary data 112 is generally stored on primarystorage device(s) 104 and is organized via a file system operating onthe client computing device 102. Thus, client computing device(s) 102and corresponding applications 110 may create, access, modify, write,delete, and otherwise use primary data 112. Primary data 112 isgenerally in the native format of the source application 110. Primarydata 112 is an initial or first stored body of data generated by thesource application 110. Primary data 112 in some cases is createdsubstantially directly from data generated by the corresponding sourceapplication 110. It can be useful in performing certain tasks toorganize primary data 112 into units of different granularities. Ingeneral, primary data 112 can include files, directories, file systemvolumes, data blocks, extents, or any other hierarchies or organizationsof data objects. As used herein, a “data object” can refer to (i) anyfile that is currently addressable by a file system or that waspreviously addressable by the file system (e.g., an archive file),and/or to (ii) a subset of such a file (e.g., a data block, an extent,etc.). Primary data 112 may include structured data (e.g., databasefiles), unstructured data (e.g., documents), and/or semi-structureddata. See, e.g., FIG. 1B.

It can also be useful in performing certain functions of system 100 toaccess and modify metadata within primary data 112. Metadata generallyincludes information about data objects and/or characteristicsassociated with the data objects. For simplicity herein, it is to beunderstood that, unless expressly stated otherwise, any reference toprimary data 112 generally also includes its associated metadata, butreferences to metadata generally do not include the primary data.Metadata can include, without limitation, one or more of the following:the data owner (e.g., the client or user that generates the data), thelast modified time (e.g., the time of the most recent modification ofthe data object), a data object name (e.g., a file name), a data objectsize (e.g., a number of bytes of data), information about the content(e.g., an indication as to the existence of a particular search term),user-supplied tags, to/from information for email (e.g., an emailsender, recipient, etc.), creation date, file type (e.g., format orapplication type), last accessed time, application type (e.g., type ofapplication that generated the data object), location/network (e.g., acurrent, past or future location of the data object and network pathwaysto/from the data object), geographic location (e.g., GPS coordinates),frequency of change (e.g., a period in which the data object ismodified), business unit (e.g., a group or department that generates,manages or is otherwise associated with the data object), aginginformation (e.g., a schedule, such as a time period, in which the dataobject is migrated to secondary or long term storage), boot sectors,partition layouts, file location within a file folder directorystructure, user permissions, owners, groups, access control lists(ACLs), system metadata (e.g., registry information), combinations ofthe same or other similar information related to the data object. Inaddition to metadata generated by or related to file systems andoperating systems, some applications 110 and/or other components ofsystem 100 maintain indices of metadata for data objects, e.g., metadataassociated with individual email messages. The use of metadata toperform classification and other functions is described in greaterdetail below.

Primary storage devices 104 storing primary data 112 may be relativelyfast and/or expensive technology (e.g., flash storage, a disk drive, ahard-disk storage array, solid state memory, etc.), typically to supporthigh-performance live production environments. Primary data 112 may behighly changeable and/or may be intended for relatively short termretention (e.g., hours, days, or weeks). According to some embodiments,client computing device 102 can access primary data 112 stored inprimary storage device 104 by making conventional file system calls viathe operating system. Each client computing device 102 is generallyassociated with and/or in communication with one or more primary storagedevices 104 storing corresponding primary data 112. A client computingdevice 102 is said to be associated with or in communication with aparticular primary storage device 104 if it is capable of one or moreof: routing and/or storing data (e.g., primary data 112) to the primarystorage device 104, coordinating the routing and/or storing of data tothe primary storage device 104, retrieving data from the primary storagedevice 104, coordinating the retrieval of data from the primary storagedevice 104, and modifying and/or deleting data in the primary storagedevice 104. Thus, a client computing device 102 may be said to accessdata stored in an associated storage device 104.

Primary storage device 104 may be dedicated or shared. In some cases,each primary storage device 104 is dedicated to an associated clientcomputing device 102, e.g., a local disk drive. In other cases, one ormore primary storage devices 104 can be shared by multiple clientcomputing devices 102, e.g., via a local network, in a cloud storageimplementation, etc. As one example, primary storage device 104 can be astorage array shared by a group of client computing devices 102, such asEMC Clariion, EMC Symmetrix, EMC Celerra, Dell EqualLogic, IBM XIV,NetApp FAS, HP EVA, and HP 3PAR.

System 100 may also include hosted services (not shown), which may behosted in some cases by an entity other than the organization thatemploys the other components of system 100. For instance, the hostedservices may be provided by online service providers. Such serviceproviders can provide social networking services, hosted email services,or hosted productivity applications or other hosted applications such assoftware-as-a-service (SaaS), platform-as-a-service (PaaS), applicationservice providers (ASPs), cloud services, or other mechanisms fordelivering functionality via a network. As it services users, eachhosted service may generate additional data and metadata, which may bemanaged by system 100, e.g., as primary data 112. In some cases, thehosted services may be accessed using one of the applications 110. As anexample, a hosted mail service may be accessed via browser running on aclient computing device 102.

Secondary Copies and Exemplary Secondary Storage Devices

Primary data 112 stored on primary storage devices 104 may becompromised in some cases, such as when an employee deliberately oraccidentally deletes or overwrites primary data 112. Or primary storagedevices 104 can be damaged, lost, or otherwise corrupted. For recoveryand/or regulatory compliance purposes, it is therefore useful togenerate and maintain copies of primary data 112. Accordingly, system100 includes one or more secondary storage computing devices 106 and oneor more secondary storage devices 108 configured to create and store oneor more secondary copies 116 of primary data 112 including itsassociated metadata. The secondary storage computing devices 106 and thesecondary storage devices 108 may be referred to as secondary storagesubsystem 118.

Secondary copies 116 can help in search and analysis efforts and meetother information management goals as well, such as: restoring dataand/or metadata if an original version is lost (e.g., by deletion,corruption, or disaster); allowing point-in-time recovery; complyingwith regulatory data retention and electronic discovery (e-discovery)requirements; reducing utilized storage capacity in the productionsystem and/or in secondary storage; facilitating organization and searchof data; improving user access to data files across multiple computingdevices and/or hosted services; and implementing data retention andpruning policies.

A secondary copy 116 can comprise a separate stored copy of data that isderived from one or more earlier-created stored copies (e.g., derivedfrom primary data 112 or from another secondary copy 116). Secondarycopies 116 can include point-in-time data, and may be intended forrelatively long-term retention before some or all of the data is movedto other storage or discarded. In some cases, a secondary copy 116 maybe in a different storage device than other previously stored copies;and/or may be remote from other previously stored copies. Secondarycopies 116 can be stored in the same storage device as primary data 112.For example, a disk array capable of performing hardware snapshotsstores primary data 112 and creates and stores hardware snapshots of theprimary data 112 as secondary copies 116. Secondary copies 116 may bestored in relatively slow and/or lower cost storage (e.g., magnetictape). A secondary copy 116 may be stored in a backup or archive format,or in some other format different from the native source applicationformat or other format of primary data 112.

Secondary storage computing devices 106 may index secondary copies 116(e.g., using a media agent 144), enabling users to browse and restore ata later time and further enabling the lifecycle management of theindexed data. After creation of a secondary copy 116 that representscertain primary data 112, a pointer or other location indicia (e.g., astub) may be placed in primary data 112, or be otherwise associated withprimary data 112, to indicate the current location of a particularsecondary copy 116. Since an instance of a data object or metadata inprimary data 112 may change over time as it is modified by application110 (or hosted service or the operating system), system 100 may createand manage multiple secondary copies 116 of a particular data object ormetadata, each copy representing the state of the data object in primarydata 112 at a particular point in time. Moreover, since an instance of adata object in primary data 112 may eventually be deleted from primarystorage device 104 and the file system, system 100 may continue tomanage point-in-time representations of that data object, even thoughthe instance in primary data 112 no longer exists. For virtual machines,the operating system and other applications 110 of client computingdevice(s) 102 may execute within or under the management ofvirtualization software (e.g., a VMM), and the primary storage device(s)104 may comprise a virtual disk created on a physical storage device.System 100 may create secondary copies 116 of the files or other dataobjects in a virtual disk file and/or secondary copies 116 of the entirevirtual disk file itself (e.g., of an entire .vmdk file).

Secondary copies 116 are distinguishable from corresponding primary data112. First, secondary copies 116 can be stored in a different formatfrom primary data 112 (e.g., backup, archive, or other non-nativeformat). For this or other reasons, secondary copies 116 may not bedirectly usable by applications 110 or client computing device 102(e.g., via standard system calls or otherwise) without modification,processing, or other intervention by system 100 which may be referred toas “restore” operations. Secondary copies 116 may have been processed bydata agent 142 and/or media agent 144 in the course of being created(e.g., compression, deduplication, encryption, integrity markers,indexing, formatting, application-aware metadata, etc.), and thussecondary copy 116 may represent source primary data 112 withoutnecessarily being exactly identical to the source.

Second, secondary copies 116 may be stored on a secondary storage device108 that is inaccessible to application 110 running on client computingdevice 102 and/or hosted service. Some secondary copies 116 may be“offline copies,” in that they are not readily available (e.g., notmounted to tape or disk). Offline copies can include copies of data thatsystem 100 can access without human intervention (e.g., tapes within anautomated tape library, but not yet mounted in a drive), and copies thatthe system 100 can access only with some human intervention (e.g., tapeslocated at an offsite storage site).

Using Intermediate Devices for Creating Secondary Copies—SecondaryStorage Computing Devices

Creating secondary copies can be challenging when hundreds or thousandsof client computing devices 102 continually generate large volumes ofprimary data 112 to be protected. Also, there can be significantoverhead involved in the creation of secondary copies 116. Moreover,specialized programmed intelligence and/or hardware capability isgenerally needed for accessing and interacting with secondary storagedevices 108. Client computing devices 102 may interact directly with asecondary storage device 108 to create secondary copies 116, but in viewof the factors described above, this approach can negatively impact theability of client computing device 102 to serve/service application 110and produce primary data 112. Further, any given client computing device102 may not be optimized for interaction with certain secondary storagedevices 108.

Thus, system 100 may include one or more software and/or hardwarecomponents which generally act as intermediaries between clientcomputing devices 102 (that generate primary data 112) and secondarystorage devices 108 (that store secondary copies 116). In addition tooff-loading certain responsibilities from client computing devices 102,these intermediate components provide other benefits. For instance, asdiscussed further below with respect to FIG. 1D, distributing some ofthe work involved in creating secondary copies 116 can enhancescalability and improve system performance. For instance, usingspecialized secondary storage computing devices 106 and media agents 144for interfacing with secondary storage devices 108 and/or for performingcertain data processing operations can greatly improve the speed withwhich system 100 performs information management operations and can alsoimprove the capacity of the system to handle large numbers of suchoperations, while reducing the computational load on the productionenvironment of client computing devices 102. The intermediate componentscan include one or more secondary storage computing devices 106 as shownin FIG. 1A and/or one or more media agents 144. Media agents arediscussed further below (e.g., with respect to FIGS. 1C-1E). Thesespecial-purpose components of system 100 comprise specialized programmedintelligence and/or hardware capability for writing to, reading from,instructing, communicating with, or otherwise interacting with secondarystorage devices 108.

Secondary storage computing device(s) 106 can comprise any of thecomputing devices described above, without limitation. In some cases,secondary storage computing device(s) 106 also include specializedhardware componentry and/or software intelligence (e.g., specializedinterfaces) for interacting with certain secondary storage device(s) 108with which they may be specially associated.

To create a secondary copy 116 involving the copying of data fromprimary storage subsystem 117 to secondary storage subsystem 118, clientcomputing device 102 may communicate the primary data 112 to be copied(or a processed version thereof generated by a data agent 142) to thedesignated secondary storage computing device 106, via a communicationpathway 114. Secondary storage computing device 106 in turn may furtherprocess and convey the data or a processed version thereof to secondarystorage device 108. One or more secondary copies 116 may be created fromexisting secondary copies 116, such as in the case of an auxiliary copyoperation, described further below.

Exemplary Primary Data and an Exemplary Secondary Copy

FIG. 1B is a detailed view of some specific examples of primary datastored on primary storage device(s) 104 and secondary copy data storedon secondary storage device(s) 108, with other components of the systemremoved for the purposes of illustration. Stored on primary storagedevice(s) 104 are primary data 112 objects including word processingdocuments 119A-B, spreadsheets 120, presentation documents 122, videofiles 124, image files 126, email mailboxes 128 (and corresponding emailmessages 129A-C), HTML/XML or other types of markup language files 130,databases 132 and corresponding tables or other data structures133A-133C. Some or all primary data 112 objects are associated withcorresponding metadata (e.g., “Meta1-11”), which may include file systemmetadata and/or application-specific metadata. Stored on the secondarystorage device(s) 108 are secondary copy 116 data objects 134A-C whichmay include copies of or may otherwise represent corresponding primarydata 112.

Secondary copy data objects 134A-C can individually represent more thanone primary data object. For example, secondary copy data object 134Arepresents three separate primary data objects 133C, 122, and 129C(represented as 133C′, 122′, and 129C′, respectively, and accompanied bycorresponding metadata Meta11, Meta3, and Meta8, respectively).Moreover, as indicated by the prime mark (′), secondary storagecomputing devices 106 or other components in secondary storage subsystem118 may process the data received from primary storage subsystem 117 andstore a secondary copy including a transformed and/or supplementedrepresentation of a primary data object and/or metadata that isdifferent from the original format, e.g., in a compressed, encrypted,deduplicated, or other modified format. For instance, secondary storagecomputing devices 106 can generate new metadata or other informationbased on said processing, and store the newly generated informationalong with the secondary copies. Secondary copy data object 134Brepresents primary data objects 120, 133B, and 119A as 120′, 133B′, and119A′, respectively, accompanied by corresponding metadata Meta2,Meta10, and Meta1, respectively. Also, secondary copy data object 134Crepresents primary data objects 133A, 119B, and 129A as 133A′, 119B′,and 129A′, respectively, accompanied by corresponding metadata Meta9,Meta5, and Meta6, respectively.

Exemplary Information Management System Architecture

System 100 can incorporate a variety of different hardware and softwarecomponents, which can in turn be organized with respect to one anotherin many different configurations, depending on the embodiment. There arecritical design choices involved in specifying the functionalresponsibilities of the components and the role of each component insystem 100. Such design choices can impact how system 100 performs andadapts to data growth and other changing circumstances. FIG. 1C shows asystem 100 designed according to these considerations and includes:storage manager 140, one or more data agents 142 executing on clientcomputing device(s) 102 and configured to process primary data 112, andone or more media agents 144 executing on one or more secondary storagecomputing devices 106 for performing tasks involving secondary storagedevices 108.

Storage Manager

Storage manager 140 is a centralized storage and/or information managerthat is configured to perform certain control functions and also tostore certain critical information about system 100—hence storagemanager 140 is said to manage system 100. As noted, the number ofcomponents in system 100 and the amount of data under management can belarge. Managing the components and data is therefore a significant task,which can grow unpredictably as the number of components and data scaleto meet the needs of the organization. For these and other reasons,according to certain embodiments, responsibility for controlling system100, or at least a significant portion of that responsibility, isallocated to storage manager 140. Storage manager 140 can be adaptedindependently according to changing circumstances, without having toreplace or re-design the remainder of the system. Moreover, a computingdevice for hosting and/or operating as storage manager 140 can beselected to best suit the functions and networking needs of storagemanager 140. These and other advantages are described in further detailbelow and with respect to FIG. 1D.

Storage manager 140 may be a software module or other application hostedby a suitable computing device. In some embodiments, storage manager 140is itself a computing device that performs the functions describedherein. Storage manager 140 comprises or operates in conjunction withone or more associated data structures such as a dedicated database(e.g., management database 146), depending on the configuration. Thestorage manager 140 generally initiates, performs, coordinates, and/orcontrols storage and other information management operations performedby system 100, e.g., to protect and control primary data 112 andsecondary copies 116. In general, storage manager 140 is said to managesystem 100, which includes communicating with, instructing, andcontrolling in some circumstances components such as data agents 142 andmedia agents 144, etc.

As shown by the dashed arrowed lines 114 in FIG. 1C, storage manager 140may communicate with, instruct, and/or control some or all elements ofsystem 100, such as data agents 142 and media agents 144. In thismanner, storage manager 140 manages the operation of various hardwareand software components in system 100. In certain embodiments, controlinformation originates from storage manager 140 and status as well asindex reporting is transmitted to storage manager 140 by the managedcomponents, whereas payload data and metadata are generally communicatedbetween data agents 142 and media agents 144 (or otherwise betweenclient computing device(s) 102 and secondary storage computing device(s)106), e.g., at the direction of and under the management of storagemanager 140. Control information can generally include parameters andinstructions for carrying out information management operations, suchas, without limitation, instructions to perform a task associated withan operation, timing information specifying when to initiate a task,data path information specifying what components to communicate with oraccess in carrying out an operation, and the like. In other embodiments,some information management operations are controlled or initiated byother components of system 100 (e.g., by media agents 144 or data agents142), instead of or in combination with storage manager 140.

According to certain embodiments, storage manager 140 provides one ormore of the following functions:

-   -   communicating with data agents 142 and media agents 144,        including transmitting instructions, messages, and/or queries,        as well as receiving status reports, index information,        messages, and/or queries, and responding to same;    -   initiating execution of information management operations;    -   initiating restore and recovery operations;    -   managing secondary storage devices 108 and inventory/capacity of        the same;    -   allocating secondary storage devices 108 for secondary copy        operations;    -   reporting, searching, and/or classification of data in system        100;    -   monitoring completion of and status reporting related to        information management operations and jobs;    -   tracking movement of data within system 100;    -   tracking age information relating to secondary copies 116,        secondary storage devices 108, comparing the age information        against retention guidelines, and initiating data pruning when        appropriate;    -   tracking logical associations between components in system 100;    -   protecting metadata associated with system 100, e.g., in        management database 146;    -   implementing job management, schedule management, event        management, alert management, reporting, job history        maintenance, user security management, disaster recovery        management, and/or user interfacing for system administrators        and/or end users of system 100;    -   sending, searching, and/or viewing of log files; and    -   implementing operations management functionality.

Storage manager 140 may maintain an associated database 146 (or “storagemanager database 146” or “management database 146”) ofmanagement-related data and information management policies 148.Database 146 is stored in computer memory accessible by storage manager140. Database 146 may include a management index 150 (or “index 150”) orother data structure(s) that may store: logical associations betweencomponents of the system; user preferences and/or profiles (e.g.,preferences regarding encryption, compression, or deduplication ofprimary data or secondary copies; preferences regarding the scheduling,type, or other aspects of secondary copy or other operations; mappingsof particular information management users or user accounts to certaincomputing devices or other components, etc.; management tasks; mediacontainerization; other useful data; and/or any combination thereof. Forexample, storage manager 140 may use index 150 to track logicalassociations between media agents 144 and secondary storage devices 108and/or movement of data to/from secondary storage devices 108. Forinstance, index 150 may store data associating a client computing device102 with a particular media agent 144 and/or secondary storage device108, as specified in an information management policy 148.

Administrators and others may configure and initiate certain informationmanagement operations on an individual basis. But while this may beacceptable for some recovery operations or other infrequent tasks, it isoften not workable for implementing on-going organization-wide dataprotection and management. Thus, system 100 may utilize informationmanagement policies 148 for specifying and executing informationmanagement operations on an automated basis. Generally, an informationmanagement policy 148 can include a stored data structure or otherinformation source that specifies parameters (e.g., criteria and rules)associated with storage management or other information managementoperations. Storage manager 140 can process an information managementpolicy 148 and/or index 150 and, based on the results, identify aninformation management operation to perform, identify the appropriatecomponents in system 100 to be involved in the operation (e.g., clientcomputing devices 102 and corresponding data agents 142, secondarystorage computing devices 106 and corresponding media agents 144, etc.),establish connections to those components and/or between thosecomponents, and/or instruct and control those components to carry outthe operation. In this manner, system 100 can translate storedinformation into coordinated activity among the various computingdevices in system 100.

Management database 146 may maintain information management policies 148and associated data, although information management policies 148 can bestored in computer memory at any appropriate location outside managementdatabase 146. For instance, an information management policy 148 such asa storage policy may be stored as metadata in a media agent database 152or in a secondary storage device 108 (e.g., as an archive copy) for usein restore or other information management operations, depending on theembodiment. Information management policies 148 are described furtherbelow. According to certain embodiments, management database 146comprises a relational database (e.g., an SQL database) for trackingmetadata, such as metadata associated with secondary copy operations(e.g., what client computing devices 102 and corresponding subclientdata were protected and where the secondary copies are stored and whichmedia agent 144 performed the storage operation(s)). This and othermetadata may additionally be stored in other locations, such as atsecondary storage computing device 106 or on the secondary storagedevice 108, allowing data recovery without the use of storage manager140 in some cases. Thus, management database 146 may comprise dataneeded to kick off secondary copy operations (e.g., storage policies,schedule policies, etc.), status and reporting information aboutcompleted jobs (e.g., status and error reports on yesterday's backupjobs), and additional information sufficient to enable restore anddisaster recovery operations (e.g., media agent associations, locationindexing, content indexing, etc.).

Storage manager 140 may include a jobs agent 156, a user interface 158,and a management agent 154, all of which may be implemented asinterconnected software modules or application programs. These aredescribed further below.

Jobs agent 156 in some embodiments initiates, controls, and/or monitorsthe status of some or all information management operations previouslyperformed, currently being performed, or scheduled to be performed bysystem 100. A job is a logical grouping of information managementoperations such as daily storage operations scheduled for a certain setof subclients (e.g., generating incremental block-level backup copies116 at a certain time every day for database files in a certaingeographical location). Thus, jobs agent 156 may access informationmanagement policies 148 (e.g., in management database 146) to determinewhen, where, and how to initiate/control jobs in system 100.

Storage Manager User Interfaces

User interface 158 may include information processing and displaysoftware, such as a graphical user interface (GUI), an applicationprogram interface (API), and/or other interactive interface(s) throughwhich users and system processes can retrieve information about thestatus of information management operations or issue instructions tostorage manager 140 and other components. Via user interface 158, usersmay issue instructions to the components in system 100 regardingperformance of secondary copy and recovery operations. For example, auser may modify a schedule concerning the number of pending secondarycopy operations. As another example, a user may employ the GUI to viewthe status of pending secondary copy jobs or to monitor the status ofcertain components in system 100 (e.g., the amount of capacity left in astorage device). Storage manager 140 may track information that permitsit to select, designate, or otherwise identify content indices,deduplication databases, or similar databases or resources or data setswithin its information management cell (or another cell) to be searchedin response to certain queries. Such queries may be entered by the userby interacting with user interface 158.

Various embodiments of information management system 100 may beconfigured and/or designed to generate user interface data usable forrendering the various interactive user interfaces described. The userinterface data may be used by system 100 and/or by another system,device, and/or software program (for example, a browser program), torender the interactive user interfaces. The interactive user interfacesmay be displayed on, for example, electronic displays (including, forexample, touch-enabled displays), consoles, etc., whetherdirect-connected to storage manager 140 or communicatively coupledremotely, e.g., via an internet connection. The present disclosuredescribes various embodiments of interactive and dynamic userinterfaces, some of which may be generated by user interface agent 158,and which are the result of significant technological development. Theuser interfaces described herein may provide improved human-computerinteractions, allowing for significant cognitive and ergonomicefficiencies and advantages over previous systems, including reducedmental workloads, improved decision-making, and the like. User interface158 may operate in a single integrated view or console (not shown). Theconsole may support a reporting capability for generating a variety ofreports, which may be tailored to a particular aspect of informationmanagement.

User interfaces are not exclusive to storage manager 140 and in someembodiments a user may access information locally from a computingdevice component of system 100. For example, some information pertainingto installed data agents 142 and associated data streams may beavailable from client computing device 102. Likewise, some informationpertaining to media agents 144 and associated data streams may beavailable from secondary storage computing device 106.

Storage Manager Management Agent

Management agent 154 can provide storage manager 140 with the ability tocommunicate with other components within system 100 and/or with otherinformation management cells via network protocols and applicationprogramming interfaces (APIs) including, e.g., HTTP, HTTPS, FTP, REST,virtualization software APIs, cloud service provider APIs, and hostedservice provider APIs, without limitation. Management agent 154 alsoallows multiple information management cells to communicate with oneanother. For example, system 100 in some cases may be one informationmanagement cell in a network of multiple cells adjacent to one anotheror otherwise logically related, e.g., in a WAN or LAN. With thisarrangement, the cells may communicate with one another throughrespective management agents 154. Inter-cell communications andhierarchy is described in greater detail in e.g., U.S. Pat. No.7,343,453.

Information Management Cell

An “information management cell” (or “storage operation cell” or “cell”)may generally include a logical and/or physical grouping of acombination of hardware and software components associated withperforming information management operations on electronic data,typically one storage manager 140 and at least one data agent 142(executing on a client computing device 102) and at least one mediaagent 144 (executing on a secondary storage computing device 106). Forinstance, the components shown in FIG. 1C may together form aninformation management cell. Thus, in some configurations, a system 100may be referred to as an information management cell or a storageoperation cell. A given cell may be identified by the identity of itsstorage manager 140, which is generally responsible for managing thecell.

Multiple cells may be organized hierarchically, so that cells mayinherit properties from hierarchically superior cells or be controlledby other cells in the hierarchy (automatically or otherwise).Alternatively, in some embodiments, cells may inherit or otherwise beassociated with information management policies, preferences,information management operational parameters, or other properties orcharacteristics according to their relative position in a hierarchy ofcells. Cells may also be organized hierarchically according to function,geography, architectural considerations, or other factors useful ordesirable in performing information management operations. For example,a first cell may represent a geographic segment of an enterprise, suchas a Chicago office, and a second cell may represent a differentgeographic segment, such as a New York City office. Other cells mayrepresent departments within a particular office, e.g., human resources,finance, engineering, etc. Where delineated by function, a first cellmay perform one or more first types of information management operations(e.g., one or more first types of secondary copies at a certainfrequency), and a second cell may perform one or more second types ofinformation management operations (e.g., one or more second types ofsecondary copies at a different frequency and under different retentionrules). In general, the hierarchical information is maintained by one ormore storage managers 140 that manage the respective cells (e.g., incorresponding management database(s) 146).

Data Agents

A variety of different applications 110 can operate on a given clientcomputing device 102, including operating systems, file systems,database applications, e-mail applications, and virtual machines, justto name a few. And, as part of the process of creating and restoringsecondary copies 116, the client computing device 102 may be tasked withprocessing and preparing the primary data 112 generated by these variousapplications 110. Moreover, the nature of the processing/preparation candiffer across application types, e.g., due to inherent structural,state, and formatting differences among applications 110 and/or theoperating system of client computing device 102. Each data agent 142 istherefore advantageously configured in some embodiments to assist in theperformance of information management operations based on the type ofdata that is being protected at a client-specific and/orapplication-specific level.

Data agent 142 is a component of information system 100 and is generallydirected by storage manager 140 to participate in creating or restoringsecondary copies 116. Data agent 142 may be a software program (e.g., inthe form of a set of executable binary files) that executes on the sameclient computing device 102 as the associated application 110 that dataagent 142 is configured to protect. Data agent 142 is generallyresponsible for managing, initiating, or otherwise assisting in theperformance of information management operations in reference to itsassociated application(s) 110 and corresponding primary data 112 whichis generated/accessed by the particular application(s) 110. Forinstance, data agent 142 may take part in copying, archiving, migrating,and/or replicating of certain primary data 112 stored in the primarystorage device(s) 104. Data agent 142 may receive control informationfrom storage manager 140, such as commands to transfer copies of dataobjects and/or metadata to one or more media agents 144. Data agent 142also may compress, deduplicate, and encrypt certain primary data 112, aswell as capture application-related metadata before transmitting theprocessed data to media agent 144. Data agent 142 also may receiveinstructions from storage manager 140 to restore (or assist inrestoring) a secondary copy 116 from secondary storage device 108 toprimary storage 104, such that the restored data may be properlyaccessed by application 110 in a suitable format as though it wereprimary data 112.

Each data agent 142 may be specialized for a particular application 110.For instance, different individual data agents 142 may be designed tohandle Microsoft Exchange data, Lotus Notes data, Microsoft Windows filesystem data, Microsoft Active Directory Objects data, SQL Server data,SharePoint data, Oracle database data, SAP database data, virtualmachines and/or associated data, and other types of data. A file systemdata agent, for example, may handle data files and/or other file systeminformation. If a client computing device 102 has two or more types ofdata 112, a specialized data agent 142 may be used for each data type.For example, to backup, migrate, and/or restore all of the data on aMicrosoft Exchange server, the client computing device 102 may use: (1)a Microsoft Exchange Mailbox data agent 142 to back up the Exchangemailboxes; (2) a Microsoft Exchange Database data agent 142 to back upthe Exchange databases; (3) a Microsoft Exchange Public Folder dataagent 142 to back up the Exchange Public Folders; and (4) a MicrosoftWindows File System data agent 142 to back up the file system of clientcomputing device 102. In this example, these specialized data agents 142are treated as four separate data agents 142 even though they operate onthe same client computing device 102. Other examples may include archivemanagement data agents such as a migration archiver or a compliancearchiver, Quick Recovery® agents, and continuous data replicationagents. Application-specific data agents 142 can provide improvedperformance as compared to generic agents. For instance, becauseapplication-specific data agents 142 may only handle data for a singlesoftware application, the design, operation, and performance of the dataagent 142 can be streamlined. The data agent 142 may therefore executefaster and consume less persistent storage and/or operating memory thandata agents designed to generically accommodate multiple differentsoftware applications 110.

Each data agent 142 may be configured to access data and/or metadatastored in the primary storage device(s) 104 associated with data agent142 and its host client computing device 102, and process the dataappropriately. For example, during a secondary copy operation, dataagent 142 may arrange or assemble the data and metadata into one or morefiles having a certain format (e.g., a particular backup or archiveformat) before transferring the file(s) to a media agent 144 or othercomponent. The file(s) may include a list of files or other metadata. Insome embodiments, a data agent 142 may be distributed between clientcomputing device 102 and storage manager 140 (and any other intermediatecomponents) or may be deployed from a remote location or its functionsapproximated by a remote process that performs some or all of thefunctions of data agent 142. In addition, a data agent 142 may performsome functions provided by media agent 144. Other embodiments may employone or more generic data agents 142 that can handle and process datafrom two or more different applications 110, or that can handle andprocess multiple data types, instead of or in addition to usingspecialized data agents 142. For example, one generic data agent 142 maybe used to back up, migrate and restore Microsoft Exchange Mailbox dataand Microsoft Exchange Database data, while another generic data agentmay handle Microsoft Exchange Public Folder data and Microsoft WindowsFile System data.

Media Agents

As noted, off-loading certain responsibilities from client computingdevices 102 to intermediate components such as secondary storagecomputing device(s) 106 and corresponding media agent(s) 144 can providea number of benefits including improved performance of client computingdevice 102, faster and more reliable information management operations,and enhanced scalability. In one example which will be discussed furtherbelow, media agent 144 can act as a local cache of recently-copied dataand/or metadata stored to secondary storage device(s) 108, thusimproving restore capabilities and performance for the cached data.

Media agent 144 is a component of system 100 and is generally directedby storage manager 140 in creating and restoring secondary copies 116.Whereas storage manager 140 generally manages system 100 as a whole,media agent 144 provides a portal to certain secondary storage devices108, such as by having specialized features for communicating with andaccessing certain associated secondary storage device 108. Media agent144 may be a software program (e.g., in the form of a set of executablebinary files) that executes on a secondary storage computing device 106.Media agent 144 generally manages, coordinates, and facilitates thetransmission of data between a data agent 142 (executing on clientcomputing device 102) and secondary storage device(s) 108 associatedwith media agent 144. For instance, other components in the system mayinteract with media agent 144 to gain access to data stored onassociated secondary storage device(s) 108, (e.g., to browse, read,write, modify, delete, or restore data). Moreover, media agents 144 cangenerate and store information relating to characteristics of the storeddata and/or metadata, or can generate and store other types ofinformation that generally provides insight into the contents of thesecondary storage devices 108—generally referred to as indexing of thestored secondary copies 116. Each media agent 144 may operate on adedicated secondary storage computing device 106, while in otherembodiments a plurality of media agents 144 may operate on the samesecondary storage computing device 106.

A media agent 144 may be associated with a particular secondary storagedevice 108 if that media agent 144 is capable of one or more of: routingand/or storing data to the particular secondary storage device 108;coordinating the routing and/or storing of data to the particularsecondary storage device 108; retrieving data from the particularsecondary storage device 108; coordinating the retrieval of data fromthe particular secondary storage device 108; and modifying and/ordeleting data retrieved from the particular secondary storage device108. Media agent 144 in certain embodiments is physically separate fromthe associated secondary storage device 108. For instance, a media agent144 may operate on a secondary storage computing device 106 in adistinct housing, package, and/or location from the associated secondarystorage device 108. In one example, a media agent 144 operates on afirst server computer and is in communication with a secondary storagedevice(s) 108 operating in a separate rack-mounted RAID-based system.

A media agent 144 associated with a particular secondary storage device108 may instruct secondary storage device 108 to perform an informationmanagement task. For instance, a media agent 144 may instruct a tapelibrary to use a robotic arm or other retrieval means to load or eject acertain storage media, and to subsequently archive, migrate, or retrievedata to or from that media, e.g., for the purpose of restoring data to aclient computing device 102. As another example, a secondary storagedevice 108 may include an array of hard disk drives or solid statedrives organized in a RAID configuration, and media agent 144 mayforward a logical unit number (LUN) and other appropriate information tothe array, which uses the received information to execute the desiredsecondary copy operation. Media agent 144 may communicate with asecondary storage device 108 via a suitable communications link, such asa SCSI or Fibre Channel link.

Each media agent 144 may maintain an associated media agent database152. Media agent database 152 may be stored to a disk or other storagedevice (not shown) that is local to the secondary storage computingdevice 106 on which media agent 144 executes. In other cases, mediaagent database 152 is stored separately from the host secondary storagecomputing device 106. Media agent database 152 can include, among otherthings, a media agent index 153 (see, e.g., FIG. 1C). In some cases,media agent index 153 does not form a part of and is instead separatefrom media agent database 152.

Media agent index 153 (or “index 153”) may be a data structureassociated with the particular media agent 144 that includes informationabout the stored data associated with the particular media agent andwhich may be generated in the course of performing a secondary copyoperation or a restore. Index 153 provides a fast and efficientmechanism for locating/browsing secondary copies 116 or other datastored in secondary storage devices 108 without having to accesssecondary storage device 108 to retrieve the information from there. Forinstance, for each secondary copy 116, index 153 may include metadatasuch as a list of the data objects (e.g., files/subdirectories, databaseobjects, mailbox objects, etc.), a logical path to the secondary copy116 on the corresponding secondary storage device 108, locationinformation (e.g., offsets) indicating where the data objects are storedin the secondary storage device 108, when the data objects were createdor modified, etc. Thus, index 153 includes metadata associated with thesecondary copies 116 that is readily available for use from media agent144. In some embodiments, some or all of the information in index 153may instead or additionally be stored along with secondary copies 116 insecondary storage device 108. In some embodiments, a secondary storagedevice 108 can include sufficient information to enable a “bare metalrestore,” where the operating system and/or software applications of afailed client computing device 102 or another target may beautomatically restored without manually reinstalling individual softwarepackages (including operating systems).

Because index 153 may operate as a cache, it can also be referred to asan “index cache.” In such cases, information stored in index cache 153typically comprises data that reflects certain particulars aboutrelatively recent secondary copy operations. After some triggeringevent, such as after some time elapses or index cache 153 reaches aparticular size, certain portions of index cache 153 may be copied ormigrated to secondary storage device 108, e.g., on a least-recently-usedbasis. This information may be retrieved and uploaded back into indexcache 153 or otherwise restored to media agent 144 to facilitateretrieval of data from the secondary storage device(s) 108. In someembodiments, the cached information may include format orcontainerization information related to archives or other files storedon storage device(s) 108.

In some alternative embodiments media agent 144 generally acts as acoordinator or facilitator of secondary copy operations between clientcomputing devices 102 and secondary storage devices 108, but does notactually write the data to secondary storage device 108. For instance,storage manager 140 (or media agent 144) may instruct a client computingdevice 102 and secondary storage device 108 to communicate with oneanother directly. In such a case, client computing device 102 transmitsdata directly or via one or more intermediary components to secondarystorage device 108 according to the received instructions, and viceversa. Media agent 144 may still receive, process, and/or maintainmetadata related to the secondary copy operations, i.e., may continue tobuild and maintain index 153. In these embodiments, payload data canflow through media agent 144 for the purposes of populating index 153,but not for writing to secondary storage device 108. Media agent 144and/or other components such as storage manager 140 may in some casesincorporate additional functionality, such as data classification,content indexing, deduplication, encryption, compression, and the like.Further details regarding these and other functions are described below.

Distributed, Scalable Architecture

As described, certain functions of system 100 can be distributed amongstvarious physical and/or logical components. For instance, one or more ofstorage manager 140, data agents 142, and media agents 144 may operateon computing devices that are physically separate from one another. Thisarchitecture can provide a number of benefits. For instance, hardwareand software design choices for each distributed component can betargeted to suit its particular function. The secondary computingdevices 106 on which media agents 144 operate can be tailored forinteraction with associated secondary storage devices 108 and providefast index cache operation, among other specific tasks. Similarly,client computing device(s) 102 can be selected to effectively serviceapplications 110 in order to efficiently produce and store primary data112.

Moreover, in some cases, one or more of the individual components ofinformation management system 100 can be distributed to multipleseparate computing devices. As one example, for large file systems wherethe amount of data stored in management database 146 is relativelylarge, database 146 may be migrated to or may otherwise reside on aspecialized database server (e.g., an SQL server) separate from a serverthat implements the other functions of storage manager 140. Thisdistributed configuration can provide added protection because database146 can be protected with standard database utilities (e.g., SQL logshipping or database replication) independent from other functions ofstorage manager 140. Database 146 can be efficiently replicated to aremote site for use in the event of a disaster or other data loss at theprimary site. Or database 146 can be replicated to another computingdevice within the same site, such as to a higher performance machine inthe event that a storage manager host computing device can no longerservice the needs of a growing system 100.

The distributed architecture also provides scalability and efficientcomponent utilization. FIG. 1D shows an embodiment of informationmanagement system 100 including a plurality of client computing devices102 and associated data agents 142 as well as a plurality of secondarystorage computing devices 106 and associated media agents 144.Additional components can be added or subtracted based on the evolvingneeds of system 100. For instance, depending on where bottlenecks areidentified, administrators can add additional client computing devices102, secondary storage computing devices 106, and/or secondary storagedevices 108. Moreover, where multiple fungible components are available,load balancing can be implemented to dynamically address identifiedbottlenecks. As an example, storage manager 140 may dynamically selectwhich media agents 144 and/or secondary storage devices 108 to use forstorage operations based on a processing load analysis of media agents144 and/or secondary storage devices 108, respectively.

Where system 100 includes multiple media agents 144 (see, e.g., FIG.1D), a first media agent 144 may provide failover functionality for asecond failed media agent 144. In addition, media agents 144 can bedynamically selected to provide load balancing. Each client computingdevice 102 can communicate with, among other components, any of themedia agents 144, e.g., as directed by storage manager 140. And eachmedia agent 144 may communicate with, among other components, any ofsecondary storage devices 108, e.g., as directed by storage manager 140.Thus, operations can be routed to secondary storage devices 108 in adynamic and highly flexible manner, to provide load balancing, failover,etc. Further examples of scalable systems capable of dynamic storageoperations, load balancing, and failover are provided in U.S. Pat. No.7,246,207.

While distributing functionality amongst multiple computing devices canhave certain advantages, in other contexts it can be beneficial toconsolidate functionality on the same computing device. In alternativeconfigurations, certain components may reside and execute on the samecomputing device. As such, in other embodiments, one or more of thecomponents shown in FIG. 1C may be implemented on the same computingdevice. In one configuration, a storage manager 140, one or more dataagents 142, and/or one or more media agents 144 are all implemented onthe same computing device. In other embodiments, one or more data agents142 and one or more media agents 144 are implemented on the samecomputing device, while storage manager 140 is implemented on a separatecomputing device, etc. without limitation.

Exemplary Types of Information Management Operations, Including StorageOperations

In order to protect and leverage stored data, system 100 can beconfigured to perform a variety of information management operations,which may also be referred to in some cases as storage managementoperations or storage operations. These operations can generally include(i) data movement operations, (ii) processing and data manipulationoperations, and (iii) analysis, reporting, and management operations.

Data Movement Operations, Including Secondary Copy Operations

Data movement operations are generally storage operations that involvethe copying or migration of data between different locations in system100. For example, data movement operations can include operations inwhich stored data is copied, migrated, or otherwise transferred from oneor more first storage devices to one or more second storage devices,such as from primary storage device(s) 104 to secondary storagedevice(s) 108, from secondary storage device(s) 108 to differentsecondary storage device(s) 108, from secondary storage devices 108 toprimary storage devices 104, or from primary storage device(s) 104 todifferent primary storage device(s) 104, or in some cases within thesame primary storage device 104 such as within a storage array.

Data movement operations can include by way of example, backupoperations, archive operations, information lifecycle managementoperations such as hierarchical storage management operations,replication operations (e.g., continuous data replication), snapshotoperations, deduplication or single-instancing operations, auxiliarycopy operations, disaster-recovery copy operations, and the like. Aswill be discussed, some of these operations do not necessarily createdistinct copies. Nonetheless, some or all of these operations aregenerally referred to as “secondary copy operations” for simplicity,because they involve secondary copies. Data movement also comprisesrestoring secondary copies.

Backup Operations

A backup operation creates a copy of a version of primary data 112 at aparticular point in time (e.g., one or more files or other data units).Each subsequent backup copy 116 (which is a form of secondary copy 116)may be maintained independently of the first. A backup generallyinvolves maintaining a version of the copied primary data 112 as well asbackup copies 116. Further, a backup copy in some embodiments isgenerally stored in a form that is different from the native format,e.g., a backup format. This contrasts to the version in primary data 112which may instead be stored in a format native to the sourceapplication(s) 110. In various cases, backup copies can be stored in aformat in which the data is compressed, encrypted, deduplicated, and/orotherwise modified from the original native application format. Forexample, a backup copy may be stored in a compressed backup format thatfacilitates efficient long-term storage. Backup copies 116 can haverelatively long retention periods as compared to primary data 112, whichis generally highly changeable. Backup copies 116 may be stored on mediawith slower retrieval times than primary storage device 104. Some backupcopies may have shorter retention periods than some other types ofsecondary copies 116, such as archive copies (described below). Backupsmay be stored at an offsite location.

Backup operations can include full backups, differential backups,incremental backups, “synthetic full” backups, and/or creating a“reference copy.” A full backup (or “standard full backup”) in someembodiments is generally a complete image of the data to be protected.However, because full backup copies can consume a relatively largeamount of storage, it can be useful to use a full backup copy as abaseline and only store changes relative to the full backup copyafterwards.

A differential backup operation (or cumulative incremental backupoperation) tracks and stores changes that occurred since the last fullbackup. Differential backups can grow quickly in size, but can restorerelatively efficiently because a restore can be completed in some casesusing only the full backup copy and the latest differential copy.

An incremental backup operation generally tracks and stores changessince the most recent backup copy of any type, which can greatly reducestorage utilization. In some cases, however, restoring can be lengthycompared to full or differential backups because completing a restoreoperation may involve accessing a full backup in addition to multipleincremental backups.

Synthetic full backups generally consolidate data without directlybacking up data from the client computing device. A synthetic fullbackup is created from the most recent full backup (i.e., standard orsynthetic) and subsequent incremental and/or differential backups. Theresulting synthetic full backup is identical to what would have beencreated had the last backup for the subclient been a standard fullbackup. Unlike standard full, incremental, and differential backups,however, a synthetic full backup does not actually transfer data fromprimary storage to the backup media, because it operates as a backupconsolidator. A synthetic full backup extracts the index data of eachparticipating subclient. Using this index data and the previously backedup user data images, it builds new full backup images (e.g., bitmaps),one for each subclient. The new backup images consolidate the index anduser data stored in the related incremental, differential, and previousfull backups into a synthetic backup file that fully represents thesubclient (e.g., via pointers) but does not comprise all its constituentdata.

Any of the above types of backup operations can be at the volume level,file level, or block level. Volume level backup operations generallyinvolve copying of a data volume (e.g., a logical disk or partition) asa whole. In a file-level backup, information management system 100generally tracks changes to individual files and includes copies offiles in the backup copy. For block-level backups, files are broken intoconstituent blocks, and changes are tracked at the block level. Uponrestore, system 100 reassembles the blocks into files in a transparentfashion. Far less data may actually be transferred and copied tosecondary storage devices 108 during a file-level copy than avolume-level copy. Likewise, a block-level copy may transfer less datathan a file-level copy, resulting in faster execution. However,restoring a relatively higher-granularity copy can result in longerrestore times. For instance, when restoring a block-level copy, theprocess of locating and retrieving constituent blocks can sometimes takelonger than restoring file-level backups.

A reference copy may comprise copy(ies) of selected objects from backedup data, typically to help organize data by keeping contextualinformation from multiple sources together, and/or help retain specificdata for a longer period of time, such as for legal hold needs. Areference copy generally maintains data integrity, and when the data isrestored, it may be viewed in the same format as the source data. Insome embodiments, a reference copy is based on a specialized client,individual subclient and associated information management policies(e.g., storage policy, retention policy, etc.) that are administeredwithin system 100.

Archive Operations

Because backup operations generally involve maintaining a version of thecopied primary data 112 and also maintaining backup copies in secondarystorage device(s) 108, they can consume significant storage capacity. Toreduce storage consumption, an archive operation according to certainembodiments creates an archive copy 116 by both copying and removingsource data. Or, seen another way, archive operations can involve movingsome or all of the source data to the archive destination. Thus, datasatisfying criteria for removal (e.g., data of a threshold age or size)may be removed from source storage. The source data may be primary data112 or a secondary copy 116, depending on the situation. As with backupcopies, archive copies can be stored in a format in which the data iscompressed, encrypted, deduplicated, and/or otherwise modified from theformat of the original application or source copy. In addition, archivecopies may be retained for relatively long periods of time (e.g., years)and, in some cases are never deleted. In certain embodiments, archivecopies may be made and kept for extended periods in order to meetcompliance regulations.

Archiving can also serve the purpose of freeing up space in primarystorage device(s) 104 and easing the demand on computational resourceson client computing device 102. Similarly, when a secondary copy 116 isarchived, the archive copy can therefore serve the purpose of freeing upspace in the source secondary storage device(s) 108. Examples of dataarchiving operations are provided in U.S. Pat. No. 7,107,298.

Snapshot Operations

Snapshot operations can provide a relatively lightweight, efficientmechanism for protecting data. From an end-user viewpoint, a snapshotmay be thought of as an “instant” image of primary data 112 at a givenpoint in time, and may include state and/or status information relativeto an application 110 that creates/manages primary data 112. In oneembodiment, a snapshot may generally capture the directory structure ofan object in primary data 112 such as a file or volume or other data setat a particular moment in time and may also preserve file attributes andcontents. A snapshot in some cases is created relatively quickly, e.g.,substantially instantly, using a minimum amount of file space, but maystill function as a conventional file system backup.

A “hardware snapshot” (or “hardware-based snapshot”) operation occurswhere a target storage device (e.g., a primary storage device 104 or asecondary storage device 108) performs the snapshot operation in aself-contained fashion, substantially independently, using hardware,firmware and/or software operating on the storage device itself. Forinstance, the storage device may perform snapshot operations generallywithout intervention or oversight from any of the other components ofthe system 100, e.g., a storage array may generate an “array-created”hardware snapshot and may also manage its storage, integrity,versioning, etc. In this manner, hardware snapshots can off-load othercomponents of system 100 from snapshot processing. An array may receivea request from another component to take a snapshot and then proceed toexecute the “hardware snapshot” operations autonomously, preferablyreporting success to the requesting component.

A “software snapshot” (or “software-based snapshot”) operation, on theother hand, occurs where a component in system 100 (e.g., clientcomputing device 102, etc.) implements a software layer that manages thesnapshot operation via interaction with the target storage device. Forinstance, the component executing the snapshot management software layermay derive a set of pointers and/or data that represents the snapshot.The snapshot management software layer may then transmit the same to thetarget storage device, along with appropriate instructions for writingthe snapshot. One example of a software snapshot product is MicrosoftVolume Snapshot Service (VSS), which is part of the Microsoft Windowsoperating system.

Some types of snapshots do not actually create another physical copy ofall the data as it existed at the particular point in time, but maysimply create pointers that map files and directories to specific memorylocations (e.g., to specific disk blocks) where the data resides as itexisted at the particular point in time. For example, a snapshot copymay include a set of pointers derived from the file system or from anapplication. In some other cases, the snapshot may be created at theblock-level, such that creation of the snapshot occurs without awarenessof the file system. Each pointer points to a respective stored datablock, so that collectively, the set of pointers reflect the storagelocation and state of the data object (e.g., file(s) or volume(s) ordata set(s)) at the point in time when the snapshot copy was created.

An initial snapshot may use only a small amount of disk space needed torecord a mapping or other data structure representing or otherwisetracking the blocks that correspond to the current state of the filesystem. Additional disk space is usually required only when files anddirectories change later on. Furthermore, when files change, typicallyonly the pointers which map to blocks are copied, not the blocksthemselves. For example for “copy-on-write” snapshots, when a blockchanges in primary storage, the block is copied to secondary storage orcached in primary storage before the block is overwritten in primarystorage, and the pointer to that block is changed to reflect the newlocation of that block. The snapshot mapping of file system data mayalso be updated to reflect the changed block(s) at that particular pointin time. In some other cases, a snapshot includes a full physical copyof all or substantially all of the data represented by the snapshot.Further examples of snapshot operations are provided in U.S. Pat. No.7,529,782. A snapshot copy in many cases can be made quickly and withoutsignificantly impacting primary computing resources because largeamounts of data need not be copied or moved. In some embodiments, asnapshot may exist as a virtual file system, parallel to the actual filesystem. Users in some cases gain read-only access to the record of filesand directories of the snapshot. By electing to restore primary data 112from a snapshot taken at a given point in time, users may also returnthe current file system to the state of the file system that existedwhen the snapshot was taken.

Replication Operations

Replication is another type of secondary copy operation. Some types ofsecondary copies 116 periodically capture images of primary data 112 atparticular points in time (e.g., backups, archives, and snapshots).However, it can also be useful for recovery purposes to protect primarydata 112 in a more continuous fashion, by replicating primary data 112substantially as changes occur. In some cases a replication copy can bea mirror copy, for instance, where changes made to primary data 112 aremirrored or substantially immediately copied to another location (e.g.,to secondary storage device(s) 108). By copying each write operation tothe replication copy, two storage systems are kept synchronized orsubstantially synchronized so that they are virtually identical atapproximately the same time. Where entire disk volumes are mirrored,however, mirroring can require significant amount of storage space andutilizes a large amount of processing resources.

According to some embodiments, secondary copy operations are performedon replicated data that represents a recoverable state, or “known goodstate” of a particular application running on the source system. Forinstance, in certain embodiments, known good replication copies may beviewed as copies of primary data 112. This feature allows the system todirectly access, copy, restore, back up, or otherwise manipulate thereplication copies as if they were the “live” primary data 112. This canreduce access time, storage utilization, and impact on sourceapplications 110, among other benefits. Based on known good stateinformation, system 100 can replicate sections of application data thatrepresent a recoverable state rather than rote copying of blocks ofdata. Examples of replication operations (e.g., continuous datareplication) are provided in U.S. Pat. No. 7,617,262.

Deduplication/Single-Instancing Operations

Deduplication or single-instance storage is useful to reduce the amountof non-primary data. For instance, some or all of the above-describedsecondary copy operations can involve deduplication in some fashion. Newdata is read, broken down into data portions of a selected granularity(e.g., sub-file level blocks, files, etc.), compared with correspondingportions that are already in secondary storage, and only new/changedportions are stored. Portions that already exist are represented aspointers to the already-stored data. Thus, a deduplicated secondary copy116 may comprise actual data portions copied from primary data 112 andmay further comprise pointers to already-stored data, which is generallymore storage-efficient than a full copy.

In order to streamline the comparison process, system 100 may calculateand/or store signatures (e.g., hashes or cryptographically unique IDs)corresponding to the individual source data portions and compare thesignatures to already-stored data signatures, instead of comparingentire data portions. In some cases, only a single instance of each dataportion is stored, and deduplication operations may therefore bereferred to interchangeably as “single-instancing” operations. Dependingon the implementation, however, deduplication operations can store morethan one instance of certain data portions, yet still significantlyreduce stored-data redundancy. Depending on the embodiment,deduplication portions such as data blocks can be of fixed or variablelength. Using variable length blocks can enhance deduplication byresponding to changes in the data stream, but can involve more complexprocessing. In some cases, system 100 utilizes a technique fordynamically aligning deduplication blocks based on changing content inthe data stream, as described in U.S. Pat. No. 8,364,652.

System 100 can deduplicate in a variety of manners at a variety oflocations. For instance, in some embodiments, system 100 implements“target-side” deduplication by deduplicating data at the media agent 144after being received from data agent 142. In some such cases, mediaagents 144 are generally configured to manage the deduplication process.For instance, one or more of the media agents 144 maintain acorresponding deduplication database that stores deduplicationinformation (e.g., data block signatures). Examples of such aconfiguration are provided in U.S. Pat. No. 9,020,900. Instead of or incombination with “target-side” deduplication, “source-side” (or“client-side”) deduplication can also be performed, e.g., to reduce theamount of data to be transmitted by data agent 142 to media agent 144.Storage manager 140 may communicate with other components within system100 via network protocols and cloud service provider APIs to facilitatecloud-based deduplication/single instancing, as exemplified in U.S. Pat.No. 8,954,446. Some other deduplication/single instancing techniques aredescribed in U.S. Pat. Pub. No. 2006/0224846 and in U.S. Pat. No.9,098,495.

Information Lifecycle Management and Hierarchical Storage Management

In some embodiments, files and other data over their lifetime move frommore expensive quick-access storage to less expensive slower-accessstorage. Operations associated with moving data through various tiers ofstorage are sometimes referred to as information lifecycle management(ILM) operations.

One type of ILM operation is a hierarchical storage management (HSM)operation, which generally automatically moves data between classes ofstorage devices, such as from high-cost to low-cost storage devices. Forinstance, an HSM operation may involve movement of data from primarystorage devices 104 to secondary storage devices 108, or between tiersof secondary storage devices 108. With each tier, the storage devicesmay be progressively cheaper, have relatively slower access/restoretimes, etc. For example, movement of data between tiers may occur asdata becomes less important over time. In some embodiments, an HSMoperation is similar to archiving in that creating an HSM copy may(though not always) involve deleting some of the source data, e.g.,according to one or more criteria related to the source data. Forexample, an HSM copy may include primary data 112 or a secondary copy116 that exceeds a given size threshold or a given age threshold. Often,and unlike some types of archive copies, HSM data that is removed oraged from the source is replaced by a logical reference pointer or stub.The reference pointer or stub can be stored in the primary storagedevice 104 or other source storage device, such as a secondary storagedevice 108 to replace the deleted source data and to point to orotherwise indicate the new location in (another) secondary storagedevice 108.

For example, files are generally moved between higher and lower coststorage depending on how often the files are accessed. When a userrequests access to HSM data that has been removed or migrated, system100 uses the stub to locate the data and may make recovery of the dataappear transparent, even though the HSM data may be stored at a locationdifferent from other source data. In this manner, the data appears tothe user (e.g., in file system browsing windows and the like) as if itstill resides in the source location (e.g., in a primary storage device104). The stub may include metadata associated with the correspondingdata, so that a file system and/or application can provide someinformation about the data object and/or a limited-functionality version(e.g., a preview) of the data object.

An HSM copy may be stored in a format other than the native applicationformat (e.g., compressed, encrypted, deduplicated, and/or otherwisemodified). In some cases, copies which involve the removal of data fromsource storage and the maintenance of stub or other logical referenceinformation on source storage may be referred to generally as “onlinearchive copies.” On the other hand, copies which involve the removal ofdata from source storage without the maintenance of stub or otherlogical reference information on source storage may be referred to as“off-line archive copies.” Examples of HSM and ILM techniques areprovided in U.S. Pat. No. 7,343,453.

Auxiliary Copy Operations

An auxiliary copy is generally a copy of an existing secondary copy 116.For instance, an initial secondary copy 116 may be derived from primarydata 112 or from data residing in secondary storage subsystem 118,whereas an auxiliary copy is generated from the initial secondary copy116. Auxiliary copies provide additional standby copies of data and mayreside on different secondary storage devices 108 than the initialsecondary copies 116. Thus, auxiliary copies can be used for recoverypurposes if initial secondary copies 116 become unavailable. Exemplaryauxiliary copy techniques are described in further detail in U.S. Pat.No. 8,230,195.

Disaster-Recovery Copy Operations

System 100 may also make and retain disaster recovery copies, often assecondary, high-availability disk copies. System 100 may createsecondary copies and store them at disaster recovery locations usingauxiliary copy or replication operations, such as continuous datareplication technologies. Depending on the particular data protectiongoals, disaster recovery locations can be remote from the clientcomputing devices 102 and primary storage devices 104, remote from someor all of the secondary storage devices 108, or both.

Data Manipulation, Including Encryption and Compression

Data manipulation and processing may include encryption and compressionas well as integrity marking and checking, formatting for transmission,formatting for storage, etc. Data may be manipulated “client-side” bydata agent 142 as well as “target-side” by media agent 144 in the courseof creating secondary copy 116, or conversely in the course of restoringdata from secondary to primary.

Encryption Operations

System 100 in some cases is configured to process data (e.g., files orother data objects, primary data 112, secondary copies 116, etc.),according to an appropriate encryption algorithm (e.g., Blowfish,Advanced Encryption Standard (AES), Triple Data Encryption Standard(3-DES), etc.) to limit access and provide data security. System 100 insome cases encrypts the data at the client level, such that clientcomputing devices 102 (e.g., data agents 142) encrypt the data prior totransferring it to other components, e.g., before sending the data tomedia agents 144 during a secondary copy operation. In such cases,client computing device 102 may maintain or have access to an encryptionkey or passphrase for decrypting the data upon restore. Encryption canalso occur when media agent 144 creates auxiliary copies or archivecopies. Encryption may be applied in creating a secondary copy 116 of apreviously unencrypted secondary copy 116, without limitation. Infurther embodiments, secondary storage devices 108 can implementbuilt-in, high performance hardware-based encryption.

Compression Operations

Similar to encryption, system 100 may also or alternatively compressdata in the course of generating a secondary copy 116. Compressionencodes information such that fewer bits are needed to represent theinformation as compared to the original representation. Compressiontechniques are well known in the art. Compression operations may applyone or more data compression algorithms. Compression may be applied increating a secondary copy 116 of a previously uncompressed secondarycopy, e.g., when making archive copies or disaster recovery copies. Theuse of compression may result in metadata that specifies the nature ofthe compression, so that data may be uncompressed on restore ifappropriate.

Data Analysis, Reporting, and Management Operations

Data analysis, reporting, and management operations can differ from datamovement operations in that they do not necessarily involve copying,migration or other transfer of data between different locations in thesystem. For instance, data analysis operations may involve processing(e.g., offline processing) or modification of already stored primarydata 112 and/or secondary copies 116. However, in some embodiments dataanalysis operations are performed in conjunction with data movementoperations. Some data analysis operations include content indexingoperations and classification operations which can be useful inleveraging data under management to enhance search and other features.

Classification Operations/Content Indexing

In some embodiments, information management system 100 analyzes andindexes characteristics, content, and metadata associated with primarydata 112 (“online content indexing”) and/or secondary copies 116(“off-line content indexing”). Content indexing can identify files orother data objects based on content (e.g., user-defined keywords orphrases, other keywords/phrases that are not defined by a user, etc.),and/or metadata (e.g., email metadata such as “to,” “from,” “cc,” “bcc,”attachment name, received time, etc.). Content indexes may be searchedand search results may be restored.

System 100 generally organizes and catalogues the results into a contentindex, which may be stored within media agent database 152, for example.The content index can also include the storage locations of or pointerreferences to indexed data in primary data 112 and/or secondary copies116. Results may also be stored elsewhere in system 100 (e.g., inprimary storage device 104 or in secondary storage device 108). Suchcontent index data provides storage manager 140 or other components withan efficient mechanism for locating primary data 112 and/or secondarycopies 116 of data objects that match particular criteria, thus greatlyincreasing the search speed capability of system 100. For instance,search criteria can be specified by a user through user interface 158 ofstorage manager 140. Moreover, when system 100 analyzes data and/ormetadata in secondary copies 116 to create an “off-line content index,”this operation has no significant impact on the performance of clientcomputing devices 102 and thus does not take a toll on the productionenvironment. Examples of content indexing techniques are provided inU.S. Pat. No. 8,170,995.

One or more components, such as a content index engine, can beconfigured to scan data and/or associated metadata for classificationpurposes to populate a database (or other data structure) ofinformation, which can be referred to as a “data classificationdatabase” or a “metabase.” Depending on the embodiment, the dataclassification database(s) can be organized in a variety of differentways, including centralization, logical sub-divisions, and/or physicalsub-divisions. For instance, one or more data classification databasesmay be associated with different subsystems or tiers within system 100.As an example, there may be a first metabase associated with primarystorage subsystem 117 and a second metabase associated with secondarystorage subsystem 118. In other cases, metabase(s) may be associatedwith individual components, e.g., client computing devices 102 and/ormedia agents 144. In some embodiments, a data classification databasemay reside as one or more data structures within management database146, may be otherwise associated with storage manager 140, and/or mayreside as a separate component. In some cases, metabase(s) may beincluded in separate database(s) and/or on separate storage device(s)from primary data 112 and/or secondary copies 116, such that operationsrelated to the metabase(s) do not significantly impact performance onother components of system 100. In other cases, metabase(s) may bestored along with primary data 112 and/or secondary copies 116. Files orother data objects can be associated with identifiers (e.g., tagentries, etc.) to facilitate searches of stored data objects. Among anumber of other benefits, the metabase can also allow efficient,automatic identification of files or other data objects to associatewith secondary copy or other information management operations. Forinstance, a metabase can dramatically improve the speed with whichsystem 100 can search through and identify data as compared to otherapproaches that involve scanning an entire file system. Examples ofmetabases and data classification operations are provided in U.S. Pat.Nos. 7,734,669 and 7,747,579.

Management and Reporting Operations

Certain embodiments leverage the integrated ubiquitous nature of system100 to provide useful system-wide management and reporting. Operationsmanagement can generally include monitoring and managing the health andperformance of system 100 by, without limitation, performing errortracking, generating granular storage/performance metrics (e.g., jobsuccess/failure information, deduplication efficiency, etc.), generatingstorage modeling and costing information, and the like. As an example,storage manager 140 or another component in system 100 may analyzetraffic patterns and suggest and/or automatically route data to minimizecongestion. In some embodiments, the system can generate predictionsrelating to storage operations or storage operation information. Suchpredictions, which may be based on a trending analysis, may predictvarious network operations or resource usage, such as network trafficlevels, storage media use, use of bandwidth of communication links, useof media agent components, etc. Further examples of traffic analysis,trend analysis, prediction generation, and the like are described inU.S. Pat. No. 7,343,453.

In some configurations having a hierarchy of storage operation cells, amaster storage manager 140 may track the status of subordinate cells,such as the status of jobs, system components, system resources, andother items, by communicating with storage managers 140 (or othercomponents) in the respective storage operation cells. Moreover, themaster storage manager 140 may also track status by receiving periodicstatus updates from the storage managers 140 (or other components) inthe respective cells regarding jobs, system components, systemresources, and other items. In some embodiments, a master storagemanager 140 may store status information and other information regardingits associated storage operation cells and other system information inits management database 146 and/or index 150 (or in another location).The master storage manager 140 or other component may also determinewhether certain storage-related or other criteria are satisfied, and mayperform an action or trigger event (e.g., data migration) in response tothe criteria being satisfied, such as where a storage threshold is metfor a particular volume, or where inadequate protection exists forcertain data. For instance, data from one or more storage operationcells is used to dynamically and automatically mitigate recognizedrisks, and/or to advise users of risks or suggest actions to mitigatethese risks. For example, an information management policy may specifycertain requirements (e.g., that a storage device should maintain acertain amount of free space, that secondary copies should occur at aparticular interval, that data should be aged and migrated to otherstorage after a particular period, that data on a secondary volumeshould always have a certain level of availability and be restorablewithin a given time period, that data on a secondary volume may bemirrored or otherwise migrated to a specified number of other volumes,etc.). If a risk condition or other criterion is triggered, the systemmay notify the user of these conditions and may suggest (orautomatically implement) a mitigation action to address the risk. Forexample, the system may indicate that data from a primary copy 112should be migrated to a secondary storage device 108 to free up space onprimary storage device 104. Examples of the use of risk factors andother triggering criteria are described in U.S. Pat. No. 7,343,453.

In some embodiments, system 100 may also determine whether a metric orother indication satisfies particular storage criteria sufficient toperform an action. For example, a storage policy or other definitionmight indicate that a storage manager 140 should initiate a particularaction if a storage metric or other indication drops below or otherwisefails to satisfy specified criteria such as a threshold of dataprotection. In some embodiments, risk factors may be quantified intocertain measurable service or risk levels. For example, certainapplications and associated data may be considered to be more importantrelative to other data and services. Financial compliance data, forexample, may be of greater importance than marketing materials, etc.Network administrators may assign priority values or “weights” tocertain data and/or applications corresponding to the relativeimportance. The level of compliance of secondary copy operationsspecified for these applications may also be assigned a certain value.Thus, the health, impact, and overall importance of a service may bedetermined, such as by measuring the compliance value and calculatingthe product of the priority value and the compliance value to determinethe “service level” and comparing it to certain operational thresholdsto determine whether it is acceptable. Further examples of the servicelevel determination are provided in U.S. Pat. No. 7,343,453.

System 100 may additionally calculate data costing and data availabilityassociated with information management operation cells. For instance,data received from a cell may be used in conjunction withhardware-related information and other information about system elementsto determine the cost of storage and/or the availability of particulardata. Exemplary information generated could include how fast aparticular department is using up available storage space, how long datawould take to recover over a particular pathway from a particularsecondary storage device, costs over time, etc. Moreover, in someembodiments, such information may be used to determine or predict theoverall cost associated with the storage of certain information. Thecost associated with hosting a certain application may be based, atleast in part, on the type of media on which the data resides, forexample. Storage devices may be assigned to a particular costcategories, for example. Further examples of costing techniques aredescribed in U.S. Pat. No. 7,343,453.

Any of the above types of information (e.g., information related totrending, predictions, job, cell or component status, risk, servicelevel, costing, etc.) can generally be provided to users via userinterface 158 in a single integrated view or console (not shown). Reporttypes may include: scheduling, event management, media management anddata aging. Available reports may also include backup history, dataaging history, auxiliary copy history, job history, library and drive,media in library, restore history, and storage policy, etc., withoutlimitation. Such reports may be specified and created at a certain pointin time as a system analysis, forecasting, or provisioning tool.Integrated reports may also be generated that illustrate storage andperformance metrics, risks and storage costing information. Moreover,users may create their own reports based on specific needs. Userinterface 158 can include an option to graphically depict the variouscomponents in the system using appropriate icons. As one example, userinterface 158 may provide a graphical depiction of primary storagedevices 104, secondary storage devices 108, data agents 142 and/or mediaagents 144, and their relationship to one another in system 100.

In general, the operations management functionality of system 100 canfacilitate planning and decision-making. For example, in someembodiments, a user may view the status of some or all jobs as well asthe status of each component of information management system 100. Usersmay then plan and make decisions based on this data. For instance, auser may view high-level information regarding secondary copy operationsfor system 100, such as job status, component status, resource status(e.g., communication pathways, etc.), and other information. The usermay also drill down or use other means to obtain more detailedinformation regarding a particular component, job, or the like. Furtherexamples are provided in U.S. Pat. No. 7,343,453.

System 100 can also be configured to perform system-wide e-discoveryoperations in some embodiments. In general, e-discovery operationsprovide a unified collection and search capability for data in thesystem, such as data stored in secondary storage devices 108 (e.g.,backups, archives, or other secondary copies 116). For example, system100 may construct and maintain a virtual repository for data stored insystem 100 that is integrated across source applications 110, differentstorage device types, etc. According to some embodiments, e-discoveryutilizes other techniques described herein, such as data classificationand/or content indexing.

Information Management Policies

An information management policy 148 can include a data structure orother information source that specifies a set of parameters (e.g.,criteria and rules) associated with secondary copy and/or otherinformation management operations.

One type of information management policy 148 is a “storage policy.”According to certain embodiments, a storage policy generally comprises adata structure or other information source that defines (or includesinformation sufficient to determine) a set of preferences or othercriteria for performing information management operations. Storagepolicies can include one or more of the following: (1) what data will beassociated with the storage policy, e.g., subclient; (2) a destinationto which the data will be stored; (3) datapath information specifyinghow the data will be communicated to the destination; (4) the type ofsecondary copy operation to be performed; and (5) retention informationspecifying how long the data will be retained at the destination (see,e.g., FIG. 1E). Data associated with a storage policy can be logicallyorganized into subclients, which may represent primary data 112 and/orsecondary copies 116. A subclient may represent static or dynamicassociations of portions of a data volume. Subclients may representmutually exclusive portions. Thus, in certain embodiments, a portion ofdata may be given a label and the association is stored as a staticentity in an index, database or other storage location. Subclients mayalso be used as an effective administrative scheme of organizing dataaccording to data type, department within the enterprise, storagepreferences, or the like. Depending on the configuration, subclients cancorrespond to files, folders, virtual machines, databases, etc. In oneexemplary scenario, an administrator may find it preferable to separatee-mail data from financial data using two different subclients.

A storage policy can define where data is stored by specifying a targetor destination storage device (or group of storage devices). Forinstance, where the secondary storage device 108 includes a group ofdisk libraries, the storage policy may specify a particular disk libraryfor storing the subclients associated with the policy. As anotherexample, where the secondary storage devices 108 include one or moretape libraries, the storage policy may specify a particular tape libraryfor storing the subclients associated with the storage policy, and mayalso specify a drive pool and a tape pool defining a group of tapedrives and a group of tapes, respectively, for use in storing thesubclient data. While information in the storage policy can bestatically assigned in some cases, some or all of the information in thestorage policy can also be dynamically determined based on criteria setforth in the storage policy. For instance, based on such criteria, aparticular destination storage device(s) or other parameter of thestorage policy may be determined based on characteristics associatedwith the data involved in a particular secondary copy operation, deviceavailability (e.g., availability of a secondary storage device 108 or amedia agent 144), network status and conditions (e.g., identifiedbottlenecks), user credentials, and the like.

Datapath information can also be included in the storage policy. Forinstance, the storage policy may specify network pathways and componentsto utilize when moving the data to the destination storage device(s). Insome embodiments, the storage policy specifies one or more media agents144 for conveying data associated with the storage policy between thesource and destination. A storage policy can also specify the type(s) ofassociated operations, such as backup, archive, snapshot, auxiliarycopy, or the like. Furthermore, retention parameters can specify howlong the resulting secondary copies 116 will be kept (e.g., a number ofdays, months, years, etc.), perhaps depending on organizational needsand/or compliance criteria.

When adding a new client computing device 102, administrators canmanually configure information management policies 148 and/or othersettings, e.g., via user interface 158. However, this can be an involvedprocess resulting in delays, and it may be desirable to begin dataprotection operations quickly, without awaiting human intervention.Thus, in some embodiments, system 100 automatically applies a defaultconfiguration to client computing device 102. As one example, when oneor more data agent(s) 142 are installed on a client computing device102, the installation script may register the client computing device102 with storage manager 140, which in turn applies the defaultconfiguration to the new client computing device 102. In this manner,data protection operations can begin substantially immediately. Thedefault configuration can include a default storage policy, for example,and can specify any appropriate information sufficient to begin dataprotection operations. This can include a type of data protectionoperation, scheduling information, a target secondary storage device108, data path information (e.g., a particular media agent 144), and thelike.

Another type of information management policy 148 is a “schedulingpolicy,” which specifies when and how often to perform operations.Scheduling parameters may specify with what frequency (e.g., hourly,weekly, daily, event-based, etc.) or under what triggering conditionssecondary copy or other information management operations are to takeplace. Scheduling policies in some cases are associated with particularcomponents, such as a subclient, client computing device 102, and thelike.

Another type of information management policy 148 is an “audit policy”(or “security policy”), which comprises preferences, rules and/orcriteria that protect sensitive data in system 100. For example, anaudit policy may define “sensitive objects” which are files or dataobjects that contain particular keywords (e.g., “confidential,” or“privileged”) and/or are associated with particular keywords (e.g., inmetadata) or particular flags (e.g., in metadata identifying a documentor email as personal, confidential, etc.). An audit policy may furtherspecify rules for handling sensitive objects. As an example, an auditpolicy may require that a reviewer approve the transfer of any sensitiveobjects to a cloud storage site, and that if approval is denied for aparticular sensitive object, the sensitive object should be transferredto a local primary storage device 104 instead. To facilitate thisapproval, the audit policy may further specify how a secondary storagecomputing device 106 or other system component should notify a reviewerthat a sensitive object is slated for transfer.

Another type of information management policy 148 is a “provisioningpolicy,” which can include preferences, priorities, rules, and/orcriteria that specify how client computing devices 102 (or groupsthereof) may utilize system resources, such as available storage oncloud storage and/or network bandwidth. A provisioning policy specifies,for example, data quotas for particular client computing devices 102(e.g., a number of gigabytes that can be stored monthly, quarterly orannually). Storage manager 140 or other components may enforce theprovisioning policy. For instance, media agents 144 may enforce thepolicy when transferring data to secondary storage devices 108. If aclient computing device 102 exceeds a quota, a budget for the clientcomputing device 102 (or associated department) may be adjustedaccordingly or an alert may trigger.

While the above types of information management policies 148 aredescribed as separate policies, one or more of these can be generallycombined into a single information management policy 148. For instance,a storage policy may also include or otherwise be associated with one ormore scheduling, audit, or provisioning policies or operationalparameters thereof. Moreover, while storage policies are typicallyassociated with moving and storing data, other policies may beassociated with other types of information management operations. Thefollowing is a non-exhaustive list of items that information managementpolicies 148 may specify:

-   -   schedules or other timing information, e.g., specifying when        and/or how often to perform information management operations;    -   the type of secondary copy 116 and/or copy format (e.g.,        snapshot, backup, archive, HSM, etc.);    -   a location or a class or quality of storage for storing        secondary copies 116 (e.g., one or more particular secondary        storage devices 108);    -   preferences regarding whether and how to encrypt, compress,        deduplicate, or otherwise modify or transform secondary copies        116;    -   which system components and/or network pathways (e.g., preferred        media agents 144) should be used to perform secondary storage        operations;    -   resource allocation among different computing devices or other        system components used in performing information management        operations (e.g., bandwidth allocation, available storage        capacity, etc.);    -   whether and how to synchronize or otherwise distribute files or        other data objects across multiple computing devices or hosted        services; and    -   retention information specifying the length of time primary data        112 and/or secondary copies 116 should be retained, e.g., in a        particular class or tier of storage devices, or within the        system 100.

Information management policies 148 can additionally specify or dependon historical or current criteria that may be used to determine whichrules to apply to a particular data object, system component, orinformation management operation, such as:

-   -   frequency with which primary data 112 or a secondary copy 116 of        a data object or metadata has been or is predicted to be used,        accessed, or modified;    -   time-related factors (e.g., aging information such as time since        the creation or modification of a data object);    -   deduplication information (e.g., hashes, data blocks,        deduplication block size, deduplication efficiency or other        metrics);    -   an estimated or historic usage or cost associated with different        components (e.g., with secondary storage devices 108);    -   the identity of users, applications 110, client computing        devices 102 and/or other computing devices that created,        accessed, modified, or otherwise utilized primary data 112 or        secondary copies 116;    -   a relative sensitivity (e.g., confidentiality, importance) of a        data object, e.g., as determined by its content and/or metadata;    -   the current or historical storage capacity of various storage        devices;    -   the current or historical network capacity of network pathways        connecting various components within the storage operation cell;    -   access control lists or other security information; and    -   the content of a particular data object (e.g., its textual        content) or of metadata associated with the data object.

Exemplary Storage Policy and Secondary Copy Operations

FIG. 1E includes a data flow diagram depicting performance of secondarycopy operations by an embodiment of information management system 100,according to an exemplary storage policy 148A. System 100 includes astorage manager 140, a client computing device 102 having a file systemdata agent 142A and an email data agent 142B operating thereon, aprimary storage device 104, two media agents 144A, 144B, and twosecondary storage devices 108: a disk library 108A and a tape library108B. As shown, primary storage device 104 includes primary data 112A,which is associated with a logical grouping of data associated with afile system (“file system subclient”), and primary data 112B, which is alogical grouping of data associated with email (“email subclient”). Thetechniques described with respect to FIG. 1E can be utilized inconjunction with data that is otherwise organized as well.

As indicated by the dashed box, the second media agent 144B and tapelibrary 108B are “off-site,” and may be remotely located from the othercomponents in system 100 (e.g., in a different city, office building,etc.). Indeed, “off-site” may refer to a magnetic tape located in remotestorage, which must be manually retrieved and loaded into a tape driveto be read. In this manner, information stored on the tape library 108Bmay provide protection in the event of a disaster or other failure atthe main site(s) where data is stored.

The file system subclient 112A in certain embodiments generallycomprises information generated by the file system and/or operatingsystem of client computing device 102, and can include, for example,file system data (e.g., regular files, file tables, mount points, etc.),operating system data (e.g., registries, event logs, etc.), and thelike. The e-mail subclient 112B can include data generated by an e-mailapplication operating on client computing device 102, e.g., mailboxinformation, folder information, emails, attachments, associateddatabase information, and the like. As described above, the subclientscan be logical containers, and the data included in the correspondingprimary data 112A and 112B may or may not be stored contiguously.

The exemplary storage policy 148A includes backup copy preferences orrule set 160, disaster recovery copy preferences or rule set 162, andcompliance copy preferences or rule set 164. Backup copy rule set 160specifies that it is associated with file system subclient 166 and emailsubclient 168. Each of subclients 166 and 168 are associated with theparticular client computing device 102. Backup copy rule set 160 furtherspecifies that the backup operation will be written to disk library 108Aand designates a particular media agent 144A to convey the data to disklibrary 108A. Finally, backup copy rule set 160 specifies that backupcopies created according to rule set 160 are scheduled to be generatedhourly and are to be retained for 30 days. In some other embodiments,scheduling information is not included in storage policy 148A and isinstead specified by a separate scheduling policy.

Disaster recovery copy rule set 162 is associated with the same twosubclients 166 and 168. However, disaster recovery copy rule set 162 isassociated with tape library 108B, unlike backup copy rule set 160.Moreover, disaster recovery copy rule set 162 specifies that a differentmedia agent, namely 144B, will convey data to tape library 108B.Disaster recovery copies created according to rule set 162 will beretained for 60 days and will be generated daily. Disaster recoverycopies generated according to disaster recovery copy rule set 162 canprovide protection in the event of a disaster or other catastrophic dataloss that would affect the backup copy 116A maintained on disk library108A.

Compliance copy rule set 164 is only associated with the email subclient168, and not the file system subclient 166. Compliance copies generatedaccording to compliance copy rule set 164 will therefore not includeprimary data 112A from the file system subclient 166. For instance, theorganization may be under an obligation to store and maintain copies ofemail data for a particular period of time (e.g., 10 years) to complywith state or federal regulations, while similar regulations do notapply to file system data. Compliance copy rule set 164 is associatedwith the same tape library 108B and media agent 144B as disasterrecovery copy rule set 162, although a different storage device or mediaagent could be used in other embodiments. Finally, compliance copy ruleset 164 specifies that the copies it governs will be generated quarterlyand retained for 10 years.

Secondary Copy Jobs

A logical grouping of secondary copy operations governed by a rule setand being initiated at a point in time may be referred to as a“secondary copy job” (and sometimes may be called a “backup job,” eventhough it is not necessarily limited to creating only backup copies).Secondary copy jobs may be initiated on demand as well. Steps 1-9 belowillustrate three secondary copy jobs based on storage policy 148A.

Referring to FIG. 1E, at step 1, storage manager 140 initiates a backupjob according to the backup copy rule set 160, which logically comprisesall the secondary copy operations necessary to effectuate rules 160 instorage policy 148A every hour, including steps 1-4 occurring hourly.For instance, a scheduling service running on storage manager 140accesses backup copy rule set 160 or a separate scheduling policyassociated with client computing device 102 and initiates a backup jobon an hourly basis. Thus, at the scheduled time, storage manager 140sends instructions to client computing device 102 (i.e., to both dataagent 142A and data agent 142B) to begin the backup job.

At step 2, file system data agent 142A and email data agent 142B onclient computing device 102 respond to instructions from storage manager140 by accessing and processing the respective subclient primary data112A and 112B involved in the backup copy operation, which can be foundin primary storage device 104. Because the secondary copy operation is abackup copy operation, the data agent(s) 142A, 142B may format the datainto a backup format or otherwise process the data suitable for a backupcopy.

At step 3, client computing device 102 communicates the processed filesystem data (e.g., using file system data agent 142A) and the processedemail data (e.g., using email data agent 142B) to the first media agent144A according to backup copy rule set 160, as directed by storagemanager 140. Storage manager 140 may further keep a record in managementdatabase 146 of the association between media agent 144A and one or moreof: client computing device 102, file system subclient 112A, file systemdata agent 142A, email subclient 112B, email data agent 142B, and/orbackup copy 116A.

The target media agent 144A receives the data-agent-processed data fromclient computing device 102, and at step 4 generates and conveys backupcopy 116A to disk library 108A to be stored as backup copy 116A, againat the direction of storage manager 140 and according to backup copyrule set 160. Media agent 144A can also update its index 153 to includedata and/or metadata related to backup copy 116A, such as informationindicating where the backup copy 116A resides on disk library 108A,where the email copy resides, where the file system copy resides, dataand metadata for cache retrieval, etc. Storage manager 140 may similarlyupdate its index 150 to include information relating to the secondarycopy operation, such as information relating to the type of operation, aphysical location associated with one or more copies created by theoperation, the time the operation was performed, status informationrelating to the operation, the components involved in the operation, andthe like. In some cases, storage manager 140 may update its index 150 toinclude some or all of the information stored in index 153 of mediaagent 144A. At this point, the backup job may be considered complete.After the 30-day retention period expires, storage manager 140 instructsmedia agent 144A to delete backup copy 116A from disk library 108A andindexes 150 and/or 153 are updated accordingly.

At step 5, storage manager 140 initiates another backup job for adisaster recovery copy according to the disaster recovery rule set 162.Illustratively this includes steps 5-7 occurring daily for creatingdisaster recovery copy 116B. Illustratively, and by way of illustratingthe scalable aspects and off-loading principles embedded in system 100,disaster recovery copy 116B is based on backup copy 116A and not onprimary data 112A and 112B.

At step 6, illustratively based on instructions received from storagemanager 140 at step 5, the specified media agent 144B retrieves the mostrecent backup copy 116A from disk library 108A.

At step 7, again at the direction of storage manager 140 and asspecified in disaster recovery copy rule set 162, media agent 144B usesthe retrieved data to create a disaster recovery copy 116B and store itto tape library 108B. In some cases, disaster recovery copy 116B is adirect, mirror copy of backup copy 116A, and remains in the backupformat. In other embodiments, disaster recovery copy 116B may be furthercompressed or encrypted, or may be generated in some other manner, suchas by using primary data 112A and 112B from primary storage device 104as sources. The disaster recovery copy operation is initiated once a dayand disaster recovery copies 116B are deleted after 60 days; indexes 153and/or 150 are updated accordingly when/after each informationmanagement operation is executed and/or completed. The present backupjob may be considered completed.

At step 8, storage manager 140 initiates another backup job according tocompliance rule set 164, which performs steps 8-9 quarterly to createcompliance copy 116C. For instance, storage manager 140 instructs mediaagent 144B to create compliance copy 116C on tape library 108B, asspecified in the compliance copy rule set 164.

At step 9 in the example, compliance copy 116C is generated usingdisaster recovery copy 116B as the source. This is efficient, becausedisaster recovery copy resides on the same secondary storage device andthus no network resources are required to move the data. In otherembodiments, compliance copy 116C is instead generated using primarydata 112B corresponding to the email subclient or using backup copy 116Afrom disk library 108A as source data. As specified in the illustratedexample, compliance copies 116C are created quarterly, and are deletedafter ten years, and indexes 153 and/or 150 are kept up-to-dateaccordingly.

Exemplary Applications of Storage Policies—Information GovernancePolicies and Classification

Again referring to FIG. 1E, storage manager 140 may permit a user tospecify aspects of storage policy 148A. For example, the storage policycan be modified to include information governance policies to define howdata should be managed in order to comply with a certain regulation orbusiness objective. The various policies may be stored, for example, inmanagement database 146. An information governance policy may align withone or more compliance tasks that are imposed by regulations or businessrequirements. Examples of information governance policies might includea Sarbanes-Oxley policy, a HIPAA policy, an electronic discovery(e-discovery) policy, and so on.

Information governance policies allow administrators to obtain differentperspectives on an organization's online and offline data, without theneed for a dedicated data silo created solely for each differentviewpoint. As described previously, the data storage systems hereinbuild an index that reflects the contents of a distributed data set thatspans numerous clients and storage devices, including both primary dataand secondary copies, and online and offline copies. An organization mayapply multiple information governance policies in a top-down manner overthat unified data set and indexing schema in order to view andmanipulate the data set through different lenses, each of which isadapted to a particular compliance or business goal. Thus, for example,by applying an e-discovery policy and a Sarbanes-Oxley policy, twodifferent groups of users in an organization can conduct two verydifferent analyses of the same underlying physical set of data/copies,which may be distributed throughout the information management system.

An information governance policy may comprise a classification policy,which defines a taxonomy of classification terms or tags relevant to acompliance task and/or business objective. A classification policy mayalso associate a defined tag with a classification rule. Aclassification rule defines a particular combination of criteria, suchas users who have created, accessed or modified a document or dataobject; file or application types; content or metadata keywords; clientsor storage locations; dates of data creation and/or access; reviewstatus or other status within a workflow (e.g., reviewed orun-reviewed); modification times or types of modifications; and/or anyother data attributes in any combination, without limitation. Aclassification rule may also be defined using other classification tagsin the taxonomy. The various criteria used to define a classificationrule may be combined in any suitable fashion, for example, via Booleanoperators, to define a complex classification rule. As an example, ane-discovery classification policy might define a classification tag“privileged” that is associated with documents or data objects that (1)were created or modified by legal department staff, or (2) were sent toor received from outside counsel via email, or (3) contain one of thefollowing keywords: “privileged” or “attorney” or “counsel,” or otherlike terms. Accordingly, all these documents or data objects will beclassified as “privileged.”

One specific type of classification tag, which may be added to an indexat the time of indexing, is an “entity tag.” An entity tag may be, forexample, any content that matches a defined data mask format. Examplesof entity tags might include, e.g., social security numbers (e.g., anynumerical content matching the formatting mask XXX-XX-XXXX), credit cardnumbers (e.g., content having a 13-16 digit string of numbers), SKUnumbers, product numbers, etc. A user may define a classification policyby indicating criteria, parameters or descriptors of the policy via agraphical user interface, such as a form or page with fields to befilled in, pull-down menus or entries allowing one or more of severaloptions to be selected, buttons, sliders, hypertext links or other knownuser interface tools for receiving user input, etc. For example, a usermay define certain entity tags, such as a particular product number orproject ID. In some implementations, the classification policy can beimplemented using cloud-based techniques. For example, the storagedevices may be cloud storage devices, and the storage manager 140 mayexecute cloud service provider API over a network to classify datastored on cloud storage devices.

Restore Operations from Secondary Copies

While not shown in FIG. 1E, at some later point in time, a restoreoperation can be initiated involving one or more of secondary copies116A, 116B, and 116C. A restore operation logically takes a selectedsecondary copy 116, reverses the effects of the secondary copy operationthat created it, and stores the restored data to primary storage where aclient computing device 102 may properly access it as primary data. Amedia agent 144 and an appropriate data agent 142 (e.g., executing onthe client computing device 102) perform the tasks needed to complete arestore operation. For example, data that was encrypted, compressed,and/or deduplicated in the creation of secondary copy 116 will becorrespondingly rehydrated (reversing deduplication), uncompressed, andunencrypted into a format appropriate to primary data. Metadata storedwithin or associated with the secondary copy 116 may be used during therestore operation. In general, restored data should be indistinguishablefrom other primary data 112. Preferably, the restored data has fullyregained the native format that may make it immediately usable byapplication 110.

As one example, a user may manually initiate a restore of backup copy116A, e.g., by interacting with user interface 158 of storage manager140 or with a web-based console with access to system 100. Storagemanager 140 may accesses data in its index 150 and/or managementdatabase 146 (and/or the respective storage policy 148A) associated withthe selected backup copy 116A to identify the appropriate media agent144A and/or secondary storage device 108A where the secondary copyresides. The user may be presented with a representation (e.g., stub,thumbnail, listing, etc.) and metadata about the selected secondarycopy, in order to determine whether this is the appropriate copy to berestored, e.g., date that the original primary data was created. Storagemanager 140 will then instruct media agent 144A and an appropriate dataagent 142 on the target client computing device 102 to restore secondarycopy 116A to primary storage device 104. A media agent may be selectedfor use in the restore operation based on a load balancing algorithm, anavailability based algorithm, or other criteria. The selected mediaagent, e.g., 144A, retrieves secondary copy 116A from disk library 108A.For instance, media agent 144A may access its index 153 to identify alocation of backup copy 116A on disk library 108A, or may accesslocation information residing on disk library 108A itself.

In some cases a backup copy 116A that was recently created or accessed,may be cached to speed up the restore operation. In such a case, mediaagent 144A accesses a cached version of backup copy 116A residing inindex 153, without having to access disk library 108A for some or all ofthe data. Once it has retrieved backup copy 116A, the media agent 144Acommunicates the data to the requesting client computing device 102.Upon receipt, file system data agent 142A and email data agent 142B mayunpack (e.g., restore from a backup format to the native applicationformat) the data in backup copy 116A and restore the unpackaged data toprimary storage device 104. In general, secondary copies 116 may berestored to the same volume or folder in primary storage device 104 fromwhich the secondary copy was derived; to another storage location orclient computing device 102; to shared storage, etc. In some cases, thedata may be restored so that it may be used by an application 110 of adifferent version/vintage from the application that created the originalprimary data 112.

Exemplary Secondary Copy Formatting

The formatting and structure of secondary copies 116 can vary dependingon the embodiment. In some cases, secondary copies 116 are formatted asa series of logical data units or “chunks” (e.g., 512 MB, 1 GB, 2 GB, 4GB, or 8 GB chunks). This can facilitate efficient communication andwriting to secondary storage devices 108, e.g., according to resourceavailability. For example, a single secondary copy 116 may be written ona chunk-by-chunk basis to one or more secondary storage devices 108. Insome cases, users can select different chunk sizes, e.g., to improvethroughput to tape storage devices. Generally, each chunk can include aheader and a payload. The payload can include files (or other dataunits) or subsets thereof included in the chunk, whereas the chunkheader generally includes metadata relating to the chunk, some or all ofwhich may be derived from the payload. For example, during a secondarycopy operation, media agent 144, storage manager 140, or other componentmay divide files into chunks and generate headers for each chunk byprocessing the files. Headers can include a variety of information suchas file and/or volume identifier(s), offset(s), and/or other informationassociated with the payload data items, a chunk sequence number, etc.Importantly, in addition to being stored with secondary copy 116 onsecondary storage device 108, chunk headers can also be stored to index153 of the associated media agent(s) 144 and/or to index 150 associatedwith storage manager 140. This can be useful for providing fasterprocessing of secondary copies 116 during browsing, restores, or otheroperations. In some cases, once a chunk is successfully transferred to asecondary storage device 108, the secondary storage device 108 returnsan indication of receipt, e.g., to media agent 144 and/or storagemanager 140, which may update their respective indexes 153, 150accordingly. During restore, chunks may be processed (e.g., by mediaagent 144) according to the information in the chunk header toreassemble the files.

Data can also be communicated within system 100 in data channels thatconnect client computing devices 102 to secondary storage devices 108.These data channels can be referred to as “data streams,” and multipledata streams can be employed to parallelize an information managementoperation, improving data transfer rate, among other advantages. Exampledata formatting techniques including techniques involving datastreaming, chunking, and the use of other data structures in creatingsecondary copies are described in U.S. Pat. Nos. 7,315,923, 8,156,086,and 8,578,120.

FIGS. 1F and 1G are diagrams of example data streams 170 and 171,respectively, which may be employed for performing informationmanagement operations. Referring to FIG. 1F, data agent 142 forms datastream 170 from source data associated with a client computing device102 (e.g., primary data 112). Data stream 170 is composed of multiplepairs of stream header 172 and stream data (or stream payload) 174. Datastreams 170 and 171 shown in the illustrated example are for asingle-instanced storage operation, and a stream payload 174 thereforemay include both single-instance (SI) data and/or non-SI data. A streamheader 172 includes metadata about the stream payload 174. This metadatamay include, for example, a length of the stream payload 174, anindication of whether the stream payload 174 is encrypted, an indicationof whether the stream payload 174 is compressed, an archive fileidentifier (ID), an indication of whether the stream payload 174 issingle instanceable, and an indication of whether the stream payload 174is a start of a block of data.

Referring to FIG. 1G, data stream 171 has the stream header 172 andstream payload 174 aligned into multiple data blocks. In this example,the data blocks are of size 64 KB. The first two stream header 172 andstream payload 174 pairs comprise a first data block of size 64 KB. Thefirst stream header 172 indicates that the length of the succeedingstream payload 174 is 63 KB and that it is the start of a data block.The next stream header 172 indicates that the succeeding stream payload174 has a length of 1 KB and that it is not the start of a new datablock. Immediately following stream payload 174 is a pair comprising anidentifier header 176 and identifier data 178. The identifier header 176includes an indication that the succeeding identifier data 178 includesthe identifier for the immediately previous data block. The identifierdata 178 includes the identifier that the data agent 142 generated forthe data block. The data stream 171 also includes other stream header172 and stream payload 174 pairs, which may be for SI data and/or non-SIdata.

FIG. 1H is a diagram illustrating data structures 180 that may be usedto store blocks of SI data and non-SI data on a storage device (e.g.,secondary storage device 108). According to certain embodiments, datastructures 180 do not form part of a native file system of the storagedevice. Data structures 180 include one or more volume folders 182, oneor more chunk folders 184/185 within the volume folder 182, and multiplefiles within chunk folder 184. Each chunk folder 184/185 includes ametadata file 186/187, a metadata index file 188/189, one or morecontainer files 190/191/193, and a container index file 192/194.Metadata file 186/187 stores non-SI data blocks as well as links to SIdata blocks stored in container files. Metadata index file 188/189stores an index to the data in the metadata file 186/187. Containerfiles 190/191/193 store SI data blocks. Container index file 192/194stores an index to container files 190/191/193. Among other things,container index file 192/194 stores an indication of whether acorresponding block in a container file 190/191/193 is referred to by alink in a metadata file 186/187. For example, data block B2 in thecontainer file 190 is referred to by a link in metadata file 187 inchunk folder 185. Accordingly, the corresponding index entry incontainer index file 192 indicates that data block B2 in container file190 is referred to. As another example, data block B1 in container file191 is referred to by a link in metadata file 187, and so thecorresponding index entry in container index file 192 indicates thatthis data block is referred to.

As an example, data structures 180 illustrated in FIG. 1H may have beencreated as a result of separate secondary copy operations involving twoclient computing devices 102. For example, a first secondary copyoperation on a first client computing device 102 could result in thecreation of the first chunk folder 184, and a second secondary copyoperation on a second client computing device 102 could result in thecreation of the second chunk folder 185. Container files 190/191 in thefirst chunk folder 184 would contain the blocks of SI data of the firstclient computing device 102. If the two client computing devices 102have substantially similar data, the second secondary copy operation onthe data of the second client computing device 102 would result in mediaagent 144 storing primarily links to the data blocks of the first clientcomputing device 102 that are already stored in the container files190/191. Accordingly, while a first secondary copy operation may resultin storing nearly all of the data subject to the operation, subsequentsecondary storage operations involving similar data may result insubstantial data storage space savings, because links to already storeddata blocks can be stored instead of additional instances of datablocks.

If the operating system of the secondary storage computing device 106 onwhich media agent 144 operates supports sparse files, then when mediaagent 144 creates container files 190/191/193, it can create them assparse files. A sparse file is a type of file that may include emptyspace (e.g., a sparse file may have real data within it, such as at thebeginning of the file and/or at the end of the file, but may also haveempty space in it that is not storing actual data, such as a contiguousrange of bytes all having a value of zero). Having container files190/191/193 be sparse files allows media agent 144 to free up space incontainer files 190/191/193 when blocks of data in container files190/191/193 no longer need to be stored on the storage devices. In someexamples, media agent 144 creates a new container file 190/191/193 whena container file 190/191/193 either includes 100 blocks of data or whenthe size of the container file 190 exceeds 50 MB. In other examples,media agent 144 creates a new container file 190/191/193 when acontainer file 190/191/193 satisfies other criteria (e.g., it containsfrom approx. 100 to approx. 1000 blocks or when its size exceedsapproximately 50 MB to 1 GB). In some cases, a file on which a secondarycopy operation is performed may comprise a large number of data blocks.For example, a 100 MB file may comprise 400 data blocks of size 256 KB.If such a file is to be stored, its data blocks may span more than onecontainer file, or even more than one chunk folder. As another example,a database file of 20 GB may comprise over 40,000 data blocks of size512 KB. If such a database file is to be stored, its data blocks willlikely span multiple container files, multiple chunk folders, andpotentially multiple volume folders. Restoring such files may requireaccessing multiple container files, chunk folders, and/or volume foldersto obtain the requisite data blocks.

Using Backup Data for Replication and Disaster Recovery (“LiveSynchronization”)

There is an increased demand to off-load resource intensive informationmanagement tasks (e.g., data replication tasks) away from productiondevices (e.g., physical or virtual client computing devices) in order tomaximize production efficiency. At the same time, enterprises expectaccess to readily-available up-to-date recovery copies in the event offailure, with little or no production downtime.

FIG. 2A illustrates a system 200 configured to address these and otherissues by using backup or other secondary copy data to synchronize asource subsystem 201 (e.g., a production site) with a destinationsubsystem 203 (e.g., a failover site). Such a technique can be referredto as “live synchronization” and/or “live synchronization replication.”In the illustrated embodiment, the source client computing devices 202 ainclude one or more virtual machines (or “VMs”) executing on one or morecorresponding VM host computers 205 a, though the source need not bevirtualized. The destination site 203 may be at a location that isremote from the production site 201, or may be located in the same datacenter, without limitation. One or more of the production site 201 anddestination site 203 may reside at data centers at known geographiclocations, or alternatively may operate “in the cloud.”

The synchronization can be achieved by generally applying an ongoingstream of incremental backups from the source subsystem 201 to thedestination subsystem 203, such as according to what can be referred toas an “incremental forever” approach. FIG. 2A illustrates an embodimentof a data flow which may be orchestrated at the direction of one or morestorage managers (not shown). At step 1, the source data agent(s) 242 aand source media agent(s) 244 a work together to write backup or othersecondary copies of the primary data generated by the source clientcomputing devices 202 a into the source secondary storage device(s) 208a. At step 2, the backup/secondary copies are retrieved by the sourcemedia agent(s) 244 a from secondary storage. At step 3, source mediaagent(s) 244 a communicate the backup/secondary copies across a networkto the destination media agent(s) 244 b in destination subsystem 203.

As shown, the data can be copied from source to destination in anincremental fashion, such that only changed blocks are transmitted, andin some cases multiple incremental backups are consolidated at thesource so that only the most current changed blocks are transmitted toand applied at the destination. An example of live synchronization ofvirtual machines using the “incremental forever” approach is found inU.S. Patent Application No. 62/265,339 entitled “Live Synchronizationand Management of Virtual Machines across Computing and VirtualizationPlatforms and Using Live Synchronization to Support Disaster Recovery.”Moreover, a deduplicated copy can be employed to further reduce networktraffic from source to destination. For instance, the system can utilizethe deduplicated copy techniques described in U.S. Pat. No. 9,239,687,entitled “Systems and Methods for Retaining and Using Data BlockSignatures in Data Protection Operations.”

At step 4, destination media agent(s) 244 b write the receivedbackup/secondary copy data to the destination secondary storagedevice(s) 208 b. At step 5, the synchronization is completed when thedestination media agent(s) and destination data agent(s) 242 b restorethe backup/secondary copy data to the destination client computingdevice(s) 202 b. The destination client computing device(s) 202 b may bekept “warm” awaiting activation in case failure is detected at thesource. This synchronization/replication process can incorporate thetechniques described in U.S. patent application Ser. No. 14/721,971,entitled “Replication Using Deduplicated Secondary Copy Data.”

Where the incremental backups are applied on a frequent, on-going basis,the synchronized copies can be viewed as mirror or replication copies.Moreover, by applying the incremental backups to the destination site203 using backup or other secondary copy data, the production site 201is not burdened with the synchronization operations. Because thedestination site 203 can be maintained in a synchronized “warm” state,the downtime for switching over from the production site 201 to thedestination site 203 is substantially less than with a typical restorefrom secondary storage. Thus, the production site 201 may flexibly andefficiently fail over, with minimal downtime and with relativelyup-to-date data, to a destination site 203, such as a cloud-basedfailover site. The destination site 203 can later be reversesynchronized back to the production site 201, such as after repairs havebeen implemented or after the failure has passed.

Integrating with the Cloud Using File System Protocols

Given the ubiquity of cloud computing, it can be increasingly useful toprovide data protection and other information management services in ascalable, transparent, and highly plug-able fashion. FIG. 2B illustratesan information management system 200 having an architecture thatprovides such advantages, and incorporates use of a standard file systemprotocol between primary and secondary storage subsystems 217, 218. Asshown, the use of the network file system (NFS) protocol (or any anotherappropriate file system protocol such as that of the Common InternetFile System (CIFS)) allows data agent 242 to be moved from the primarystorage subsystem 217 to the secondary storage subsystem 218. Forinstance, as indicated by the dashed box 206 around data agent 242 andmedia agent 244, data agent 242 can co-reside with media agent 244 onthe same server (e.g., a secondary storage computing device such ascomponent 106), or in some other location in secondary storage subsystem218.

Where NFS is used, for example, secondary storage subsystem 218allocates an NFS network path to the client computing device 202 or toone or more target applications 210 running on client computing device202. During a backup or other secondary copy operation, the clientcomputing device 202 mounts the designated NFS path and writes data tothat NFS path. The NFS path may be obtained from NFS path data 215stored locally at the client computing device 202, and which may be acopy of or otherwise derived from NFS path data 219 stored in thesecondary storage subsystem 218.

Write requests issued by client computing device(s) 202 are received bydata agent 242 in secondary storage subsystem 218, which translates therequests and works in conjunction with media agent 244 to process andwrite data to a secondary storage device(s) 208, thereby creating abackup or other secondary copy. Storage manager 240 can include apseudo-client manager 217, which coordinates the process by, among otherthings, communicating information relating to client computing device202 and application 210 (e.g., application type, client computing deviceidentifier, etc.) to data agent 242, obtaining appropriate NFS path datafrom the data agent 242 (e.g., NFS path information), and deliveringsuch data to client computing device 202.

Conversely, during a restore or recovery operation client computingdevice 202 reads from the designated NFS network path, and the readrequest is translated by data agent 242. The data agent 242 then workswith media agent 244 to retrieve, re-process (e.g., re-hydrate,decompress, decrypt), and forward the requested data to client computingdevice 202 using NFS.

By moving specialized software associated with system 200 such as dataagent 242 off the client computing devices 202, the illustrativearchitecture effectively decouples the client computing devices 202 fromthe installed components of system 200, improving both scalability andplug-ability of system 200. Indeed, the secondary storage subsystem 218in such environments can be treated simply as a read/write NFS targetfor primary storage subsystem 217, without the need for informationmanagement software to be installed on client computing devices 202. Asone example, an enterprise implementing a cloud production computingenvironment can add VM client computing devices 202 without installingand configuring specialized information management software on theseVMs. Rather, backups and restores are achieved transparently, where thenew VMs simply write to and read from the designated NFS path. Anexample of integrating with the cloud using file system protocols orso-called “infinite backup” using NFS share is found in U.S. PatentApplication No. 62/294,920, entitled “Data Protection Operations Basedon Network Path Information.” Examples of improved data restorationscenarios based on network-path information, including using storedbackups effectively as primary data sources, may be found in U.S. PatentApplication No. 62/297,057, entitled “Data Restoration Operations Basedon Network Path Information.”

Highly Scalable Managed Data Pool Architecture

Enterprises are seeing explosive data growth in recent years, often fromvarious applications running in geographically distributed locations.FIG. 2C shows a block diagram of an example of a highly scalable,managed data pool architecture useful in accommodating such data growth.The illustrated system 200, which may be referred to as a “web-scale”architecture according to certain embodiments, can be readilyincorporated into both open compute/storage and common-cloudarchitectures.

The illustrated system 200 includes a grid 245 of media agents 244logically organized into a control tier 231 and a secondary or storagetier 233. Media agents assigned to the storage tier 233 can beconfigured to manage a secondary storage pool 208 as a deduplicationstore, and be configured to receive client write and read requests fromthe primary storage subsystem 217, and direct those requests to thesecondary tier 233 for servicing. For instance, media agents CMA1-CMA3in the control tier 231 maintain and consult one or more deduplicationdatabases 247, which can include deduplication information (e.g., datablock hashes, data block links, file containers for deduplicated files,etc.) sufficient to read deduplicated files from secondary storage pool208 and write deduplicated files to secondary storage pool 208. Forinstance, system 200 can incorporate any of the deduplication systemsand methods shown and described in U.S. Pat. No. 9,020,900, entitled“Distributed Deduplicated Storage System,” and U.S. Pat. Pub. No.2014/0201170, entitled “High Availability Distributed DeduplicatedStorage System.”

Media agents SMA1-SMA6 assigned to the secondary tier 233 receive writeand read requests from media agents CMA1-CMA3 in control tier 231, andaccess secondary storage pool 208 to service those requests. Mediaagents CMA1-CMA3 in control tier 231 can also communicate with secondarystorage pool 208, and may execute read and write requests themselves(e.g., in response to requests from other control media agentsCMA1-CMA3) in addition to issuing requests to media agents in secondarytier 233. Moreover, while shown as separate from the secondary storagepool 208, deduplication database(s) 247 can in some cases reside instorage devices in secondary storage pool 208.

As shown, each of the media agents 244 (e.g., CMA1-CMA3, SMA1-SMA6,etc.) in grid 245 can be allocated a corresponding dedicated partition251A-251I, respectively, in secondary storage pool 208. Each partition251 can include a first portion 253 containing data associated with(e.g., stored by) media agent 244 corresponding to the respectivepartition 251. System 200 can also implement a desired level ofreplication, thereby providing redundancy in the event of a failure of amedia agent 244 in grid 245. Along these lines, each partition 251 canfurther include a second portion 255 storing one or more replicationcopies of the data associated with one or more other media agents 244 inthe grid.

System 200 can also be configured to allow for seamless addition ofmedia agents 244 to grid 245 via automatic configuration. As oneillustrative example, a storage manager (not shown) or other appropriatecomponent may determine that it is appropriate to add an additional nodeto control tier 231, and perform some or all of the following: (i)assess the capabilities of a newly added or otherwise availablecomputing device as satisfying a minimum criteria to be configured as orhosting a media agent in control tier 231; (ii) confirm that asufficient amount of the appropriate type of storage exists to supportan additional node in control tier 231 (e.g., enough disk drive capacityexists in storage pool 208 to support an additional deduplicationdatabase 247); (iii) install appropriate media agent software on thecomputing device and configure the computing device according to apre-determined template; (iv) establish a partition 251 in the storagepool 208 dedicated to the newly established media agent 244; and (v)build any appropriate data structures (e.g., an instance ofdeduplication database 247). An example of highly scalable managed datapool architecture or so-called web-scale architecture for storage anddata management is found in U.S. Patent Application No. 62/273,286entitled “Redundant and Robust Distributed Deduplication Data StorageSystem.”

The embodiments and components thereof disclosed in FIGS. 2A, 2B, and2C, as well as those in FIGS. 1A-1H, may be implemented in anycombination and permutation to satisfy data storage management andinformation management needs at one or more locations and/or datacenters.

Interoperability Between Components of a Data Storage Management Systemand Appliances for Data Storage and Deduplication

The following paragraphs provide a detailed description of severalembodiments of interoperability between certain components of a datastorage management system (such as a storage manager component and/ormedia agent components) and appliances with data storage anddeduplication capabilities that are used for efficient storage ofsecondary and tertiary copies of data (hereinafter “deduplicationappliances”). Storage manager 340, media agent 344, media agent index353, and deduplication appliances 380 are illustrative components thatinteroperate according the illustrative embodiments herein.

FIG. 3A depicts a data storage management system 300 forinteroperability between storage management components and one or moreappliances for data storage and deduplication (e.g., deduplicationappliance 380), according to an illustrative embodiment of the presentinvention. FIG. 3A shows a logical view of data flow (boldunidirectional arrows) in system 300 when making secondary and/ortertiary copies to be stored to deduplication appliance(s) 380. FIG. 3Adepicts: primary data 112, data agent 142, storage manager 340comprising management database 346, media agents 344-1 and 344-2, mediaagent indexes 353-1 and 353-2, and deduplication appliances 380-1 and380-2, each deduplication appliance comprising one or more storagedevices 390 (e.g., 390-1, 390-2, respectively). Communication pathways114 and 376 are also depicted. The underlying physical infrastructurerequired to support the depicted communication pathways andinterconnectivity is well known in the art. There is no limitation onthe number of data agents 142, media agents 344, and deduplicationappliances 380 that can be configured within an illustrative system 300.Deduplication appliances 380 are shown here as part of system 300, butin other embodiments they are in communication with but not part ofsystem 300.

Primary data 112 and data agent 142 are described in more detailelsewhere herein. Likewise, communication pathways 114, which connectstorage manager 340 with data agent 142 and media agent 344 as well asconnecting media agent 344 with data agent 142, are described in moredetail elsewhere herein.

System 300 is a data storage management system analogous to system 100and includes features and components for protecting and managing data,comprising storage manager 340, data agents 142, and media agents 344.Media agents 144 also are included in some embodiments.

Storage manager 340 is analogous to storage manager 140 and additionallycomprises features for supporting interoperability with deduplicationappliances (e.g., 380) that are used for efficient storage of secondaryand tertiary copies of data. Storage manager 340 is generally embodiedas software that executes on a computing device having one or moreprocessors and computer memory, which can be implemented in a datacenter or in a cloud computing environment without limitation. Storagemanager 340 manages system 300 as a whole, including managing storagemanagement operations (e.g., making secondary and tertiary copies,restoring data, indexing and classifying data, tracking copies andcomponents, and tracking status of storage management operations andjobs, etc.).

For supporting interoperability with deduplication appliances (e.g.,380), storage manager 340 comprises features that include one or more:

-   -   administrative parameters that identify and distinguish        deduplication appliances (e.g., 380) from ordinary data storage        devices that lack deduplication and other native features;    -   specialized instructions that direct media agents 344 to        segregate payload data apart from metadata apart from indexing        information when transmitting to a deduplication appliance        (e.g., 380);    -   specialized instructions that inform media agents 344 that a        storage destination at deduplication appliance 380 includes        deduplication features (and other native features such as        compression and/or encryption) and thus the media agent 344        should not deduplicate (or encrypt/compress) before transmitting        data to the deduplication appliance 380;    -   and    -   other features as seen in the accompanying figures and described        in more detail elsewhere herein.

Management database 346 is analogous to management database 146 andadditionally comprises information needed for and resulting frominteroperability with deduplication appliances (e.g., 380). For example,one or more of: storage policies for storing secondary and tertiarycopies to a deduplication appliance (e.g., 380); deduplication status ofsecondary and tertiary copies stored to a deduplication appliance (e.g.,380); job status for backup jobs to deduplication appliancedestinations; tracking information for secondary/tertiary copies storedat a deduplication appliance (e.g., 380); etc. Management database 346is logically part of storage manager 340. Management database 346 isshown here as part of storage manager 340, but in other embodimentsmanagement database 346 is associated with but not physically part ofstorage manager 340.

Media agent 344 (e.g., 344-1, 344-2) is analogous to media agent 144 andadditionally comprises features for interoperability with deduplicationappliances (e.g., 380) in contrast with ordinary secondary storagedevices 108. Accordingly, media agent 344 is configured to:

-   -   receive and interpret instructions from storage manager 340        indicating that data is to be backed up to or restored from        deduplication appliance 380 in contrast to ordinary secondary        storage 108;    -   recognize that a deduplication appliance (e.g., 380) is a        designated destination for storing secondary and/or tertiary        copies;    -   recognize that a copy to be restored is currently in a        deduplication appliance (e.g., 380);    -   recognize and segregate payload data from metadata from index        information when transmitting to a deduplication appliance        (e.g., 380);    -   instruct the destination deduplication appliance (e.g., 380) to        deduplicate certain data such as payload data chunks, and not to        deduplicate certain other data such as metadata, pointers, and        index information when making copies;    -   recognize that the deduplication appliance (e.g., 380) is        capable of natively deduplicating and/or rehydrating and/or        moving data it stores, and therefore avoiding data flowing        through media agent 344 when generating synthetic-full and        auxiliary copies and other tertiary copies in conjunction with a        deduplication appliance (e.g., 380);    -   recognize that the deduplication appliance (e.g., 380) will        rehydrate data chunks on restore operations, thus avoiding the        media agent 344 having to rehydrate;    -   recognize that the deduplication appliance (e.g., 380) also has        native encryption and compression features, thus avoiding media        agent 344 having to compress/encrypt data destined for the        deduplication appliance;    -   and    -   other features as seen in the accompanying figures and described        in more detail elsewhere herein.

Illustratively, when media agent 344 supplies instructions todeduplicate to deduplication appliance 380, media agent 344 indicateswhether deduplication should be based on fixed block size or variableblock size; illustratively the choice of fixed-versus-variable is basedon the type of data agent 142 that is involved in the backup job. Forexample, backups for SAP HANA and Virtual Server are illustrativelybased on fixed block size deduplication based on the respective dataagent 142, whereas other backups using other types of data agents 142use variable size block deduplication (e.g., data agents for SQL Serverdatabase, Oracle database, Sybase database, DB2 database, Informixdatabase, Postgres database, File system).

Media agent index 353 (e.g., 353-1, 353-2) (“index 353”) is analogous tomedia agent index 153 and additionally comprises information forsupporting interoperability with deduplication appliances (e.g.,380)—see, e.g., FIG. 5A. Illustratively, index 353 resides on the samecomputing device that hosts media agent 344—see, e.g., FIG. 3B. Mediaagent index 353 is associated with media agent 344 and is maintained andused by media agent 344.

Deduplication appliance 380 (e.g., 380-1, 380-2) is a device thatcomprises one or more data storage devices (e.g., 390) and alsocomprises features for: deduplicating data stored therein and fortracking the deduplicated data; copying and moving data internally andto/from other deduplication appliances 380; selectively deduplicatingsome data and not other data; rehydrating data being moved and/orrestored from deduplication appliance 380; and other native featuressuch as compression and encryption. Examples of a deduplicationappliance 380 include: HPE StoreOnce systems from Hewlett PackardEnterprise of Palo Alto, Calif., USA. Examples of a data storagemanagement system 300 for interoperating with HPE StoreOnce systemsinclude Commvault Complete software from Commvault Systems, Inc. ofTinton Falls, N.J., USA. In other embodiments, Commvault Completesoftware from Commvault Systems, Inc. also interoperates with appliancesother than HPE StoreOnce. The example embodiments given herein forillustration purposes do not limit the features/capabilities ofdeduplication appliance 380 and/or of data storage components 340, 344,346, 353, and/or 142.

Storage devices 390 (e.g., 390-1, 390-2) are components of deduplicationappliance 380 and are used for storing data at deduplication appliance380. A given deduplication appliance 380 has one or more storage devices390, depending on configuration and storage capacity, withoutlimitation.

Communication pathway 376 enables media agent 344 (e.g., 344-1) tocommunicate with deduplication appliance 380. A suitable protocol suchas an Application Programming Interface (“API”), which is well known inthe art, enables deduplication appliance 380 to communicate with mediaagent 344 over communication pathway 376.

The bold arrows in the present figure provide a logical view of how dataflows from a source of primary data 112 via data agent 142 via mediaagent 344-1 and on to deduplication appliance 380-1 to be stored in datastorage device 390-1 in the form of secondary and/or tertiary copies. Insome embodiments, data also flows from a first deduplication appliance380-1 to a second deduplication appliance 380-2, without flowing throughmedia agent 344-2. In restore scenarios, the data flow shown here isreversed as data is recovered from one more deduplication appliances 380and is restored as primary data 112 (see also FIG. 9 ).

FIG. 3B depicts some details of system 300 including a clientconfiguration and media agent connectivity to a deduplication appliance380. FIG. 3B depicts: client computing device 102 comprisingapplication/file system 110, primary data 112, data agent 142, mediaagent 344, and media agent index 353; deduplication appliance 380comprising one or more data storage devices 390; and communicationpathway 376 comprising pathway 376Cmd and pathway 376Data. The boldarrows in the present figure provide a logical view of how data flowsfrom a source of primary data 112 via data agent 142 via media agent 344and via communication pathway 376Data to deduplication appliance 380 tobe stored to data storage device 390.

Client computing device 102, application and/or file system 110, primarydata 112, data agent 142, media agent 344, media agent index 353,deduplication appliance 380, and data storage device(s) 390 aredescribed in more detail elsewhere herein. According to an illustrativeembodiment, media agent 344 co-resides with data agent 142 on clientcomputing device 102, which comprises one or more processors andcomputer memory and also hosts an application and/or file system 110,which directly accesses and consumes primary data 112. This arrangementadvantageously provides improved performance and lower cost of ownershipby avoiding the need for a dedicated secondary storage computing device(e.g., 106) to host media agent 344; however, the invention is not solimited. In some embodiments, one or more media agents 344 are hosted byrespective dedicated secondary storage computing devices 106 apart fromclient computing device 102.

Communication pathway 376 comprises pathway 376Cmd and pathway 376Data.Communication pathway 376Cmd represents a command interface betweendeduplication appliance 380 and media agent 344, used by an ApplicationProgramming Interface (“API”), which is well known in the art.Communication pathway 376Cmd generally comprises commands, instructions,and/or queries issued by media agent 344 to deduplication appliance 380and responses (e.g., confirmation messages, status reports, queryresponses, etc.) issued by deduplication appliance 380—andillustratively does not include payload data, metadata content, and/orcopies, which are transmitted over communication pathway 376Datainstead.

Communication pathway 376Data generally comprises data being transmittedto/from deduplication appliance 380, such as payload data, metadatacontent, pointers, and index information. Here, the data flow ofcommunication pathway 376Data is shown from media agent 344 todeduplication appliance 380 to illustrate making copies based on primarydata 112. In restore scenarios, the data flow direction is reversed(see, e.g., FIG. 9 ). According to the illustrative embodiments depictedherein, communication pathway 376Data comprises one or more datastreams, each data stream comprising different kinds of data (e.g.,payload data, metadata, index information)—see, e.g., FIGS. 5A-8 .

FIG. 4 depicts a high level view of illustrative logic used by anexample deduplication appliance 380. FIG. 4 depicts: deduplicationappliance 380 comprising native appliance data processing logic 401 andstorage device 390 which comprises data 492 in deduplicated, encrypted,compressed, and/or raw form. Logical blocks 402 and 406 and logical datapathways 404 and 408 are also depicted.

Native appliance data processing logic 401 is shown here as a high-levelillustration of how deduplication appliance 380 handles certain databefore storing it internally to data storage device(s) 390. Logic 401 ismerely a logical view and can be implemented in any suitable mannerknown in the art according to the particular architecture andcapabilities of a given deduplication appliance 380.

At block 402, which represents a decision point, deduplication appliance380 (e.g., using logic 401) determines whether a set of data (e.g., datastream, data chunk, data block, data extent, etc.) should be subjectedto deduplication by deduplication appliance 380. The determination isillustratively based upon instructions received from media agent 344(e.g., using communication pathway 376Cmd); in other embodiments thedetermination is based on indicators embedded in the set of data (e.g.,received via communication pathway 376Data). If deduplication is to beapplied, control passes to block 406; otherwise, the set of data is“passed through” to storage 390 without deduplication.

Data that is usually unique (e.g., due to time stamps, indexing entries,header details, access control lists, pointers, etc.) does not make anefficient deduplication target, and therefore making the attempt todeduplicate can be wasteful as it will not yield substantialresults—hence logical pathway 404 is used to “store withoutdeduplication.” According to illustrative embodiments, media agent 344instructs that the following kinds of data not be subjected todeduplication at deduplication appliance 380: metadata content andpointers to other data streams and to data within data streams (see,e.g., data streams 520, 530). On the other hand, payload data is morelikely to be duplicative of other data and therefore is a good candidatefor deduplication—hence block 406 and logical pathway 408 are used for“store deduplicated.”

At block 406, deduplication appliance 380 (e.g., using logic 401)applies deduplication to the set of data using its own nativededuplication techniques. Accordingly, deduplication appliance 380follows logical pathway 408 and stores the set of data in deduplicatedform to storage device(s) 390. Illustratively, when media agent 344supplies instructions to deduplicate to deduplication appliance 380,media agent indicates whether deduplication should be based on fixedblock size or variable block size; illustratively the choice offixed-versus-variable is based on the type of data agent 142 that isinvolved in the backup operation.

Deduplication appliance 380 also comprises other native datamanipulation features besides deduplication, which illustrativelyinclude compression and encryption. Media agent 344 instructsdeduplication appliance 380 to compress and/or encrypt data using theAPI. Thus, the native features of deduplication appliance 380, includingdeduplication, compression, encryption, and the correspondingrehydration, decompression, and decryption features off-load media agent344 from carrying out these computationally demanding operations.

Stored data 492 is a logical depiction of data that is stored withindeduplication appliance 380, which includes data in any suitable form,including one or more of raw, compressed, encrypted, deduplicated, etc.For example, secondary copies 519, 629, 729, and 829 all are part ofstored data 492. How deduplication appliance 380 manages and tracks thedata it stores is not shown here. However, according to an illustrativeembodiment media agent 344 is aware of storage resources 390 atdeduplication appliance 380 and can direct data to be stored to certainspecific locations and/or using offsets within data storage device(s)390 and/or using offsets with data streams, which can be mapped tostorage locations. Thus, media agent 344 “knows” where certain datachunks are to be stored.

FIG. 5A depicts a logical view of a backup operation in system 300 forgenerating secondary copies based on primary data by segregatingpayload, metadata, and index information into separate data streamstransmitted to an example deduplication appliance 380. This scenario isused when making one or more initial secondary copies (e.g., 519-1 . . .519-N) based on primary data, wherein the secondary copies are stored atdeduplication appliance 380. FIG. 5A depicts: media agent 344; mediaagent index 353 comprising an illustrative data structure 553;deduplication appliance 380 comprising secondary copies 519-1 . . .519-N; and data streams 510, 520, and 530 that originate at media agent344 and terminate at deduplication appliance 380 over communicationpathway 376Data.

Media agent 344 generates three distinct data streams comprisingmutually segregated types of data (e.g., payload, metadata content,index information). The distinct data streams 510, 520, and 530 arecollectively transmitted to deduplication appliance 380 viacommunication pathway 376Data. This approach is distinguishable from thetraditional approach used by media agents 144, in which payload andmetadata are interleaved within the same data stream as shown in FIGS.1F and 1G. That traditional approach is advantageous with ordinary datastorage devices 108, where control over the data formatting andorganization resides with media agent 144, but is not advantageous forthe illustrative deduplication appliance 380.

Data stream 510 (“payload data stream 510”) originates at media agent344. Data stream 510 comprises a plurality of data chunks that compriseonly payload data extracted from the data source (e.g., from primarydata 112, from a snapshot of primary data 112). Data sourcesillustratively include data files stored as primary data 112. Mediaagent 344 is capable of determining what portions of source data (e.g.,what parts of a data file) is payload data versus metadata. Accordingly,media agent 344 segregates the payload data into data chunks that formdata stream 510. Each payload data chunk is uniquely identified. Payloaddata chunks in data stream 510 can be of any size without limitation.More details are given in the next figure.

Secondary copies 519 (e.g., 519-1 . . . 519-N), are stored atdeduplication appliance 380 in one or more storage devices 390 (notshown in the present figure). Each secondary copy 519 is based onprimary data 112. As explained in more detail elsewhere herein, dataagent 142 and media agent 344 are responsible for generating a secondarycopy 519 based on primary data 112, but after receiving data streams510, 520, and 530 from media agent 344 deduplication appliance 380 alsocontributes one or more of its own native features, such as storage,tracking, deduplication, compression, encryption, etc. Secondary copies519 are sources of data for tertiary copies such as 629, 729, and/or829. Secondary copies 519 can be restored to a native data format thatis directly accessible as primary data 112 to an application/file system110 that executes at a client computing device 102—whether the same asthe original source primary data 112 or elsewhere. There is no limit onhow many secondary copies 519 are generated and stored to deduplicationappliance 380 according to the illustrative embodiments.

A backup job based on source primary data 112 generates the depicteddata streams 510, 520, and 530, which are transmitted by media agent 344to deduplication appliance 380. Deduplication appliance 380 appliesfurther processing to the received data streams (see, e.g., FIGS. 4, 10,11 ) and stores the resultant secondary copy(ies) 519 to one or moredata storage devices 390. Specific destination storage locations areinstructed by media agent 344 according to an illustrative embodiment,but in some embodiments deduplication appliance 380 reports storagelocations to media agent 344, which in turn updates its associated mediaagent index agent index 353.

Data stream 520 (“metadata stream 520”) originates at media agent 344.Data stream 520 comprises a plurality of data chunks each of whichcorresponds to one or more payload data chunks in data stream 510. Eachdata chunk in data stream 520 (hereinafter “meta-chunk”) comprises:

-   -   (i) metadata content extracted from the backup source (e.g.,        file properties, file header information, access control lists,        etc.), and    -   (ii) one or more pointers to payload data chunks in data stream        510 that belong to the same source (e.g., payload for the same        data file from which the metadata content was extracted).

Thus, meta-chunks in data stream 520 directly relate to payload datachunks in data stream 510. For any given data source, such as a file, adatabase, etc., payload data is transmitted to deduplication appliance380 in data stream 510, while its associated metadata content issegregated into and separately transmitted in data stream 520 along withpointers to the payload data chunks in data stream 510.

Data stream 530 (“index data stream 530” or “index stream 530”)originates at media agent 344. Data stream 530 comprises a plurality ofdata chunks each of which corresponds to a meta-chunk in data stream520. Each data chunk in data stream 530 (hereinafter “index chunk”)comprises index information generated by media agent 344 in reference tometa-chunks in data stream 520. Media agent 344 indexes the meta-chunksof data stream 520 into an illustrative data structure 553 maintained inmedia agent index 353. The index information enables media agent 344 totrack and find meta-chunks transmitted to deduplication appliance 380 indata stream 520, for example keeping identifiers of and pointers to eachmeta-chunk, which in turn is associated with its source file. Thisindexing information is packed into the illustrative index chunks ofindex stream 530. By storing this information at deduplication appliance380, system 300 enables another media agent 344 to extract data fromdeduplication appliance 380. See, e.g., FIGS. 6-8 .

Data structure 553 is illustratively maintained in media agent index353, but the invention is not so limited. The information depicted indata structure 553 can be organized and stored by media agent 344 in anysuitable fashion and location readily accessible to media agent 344 suchas in index 353. Table 553 is an example of data that media agent 344generates and stores for interoperability with deduplication appliance380. Table 553 comprises index information (or “indexing information”)that media agent 344 generates and/or retains. Illustratively, table 553comprises indexing information pertaining to metadata streams 520. Forexample, table 553 comprises one or more rows for each file backed upvia media agent 344, e.g., file F1, file F2 . . . File FN. For eachbacked up file, table 553 stores an offset value and a meta-chunk IDwithin a metadata stream 520 in which the given meta-chunk wastransmitted. Thus, each meta-chunk is uniquely identified (e.g., Ch1)and located (e.g., Off1) within the data stream 520 that carried it todeduplication appliance 380. This information enables data agent 344 tolocate each meta-chunk at deduplication appliance 380. From there, mediaagent 344 can extract pointers to corresponding payload data chunksstored at deduplication appliance 380. The information indexed to datastructure 553 is thus used in index stream 530, as shown in more detailin the next figure.

Optionally, media agent 344 also keeps a copy of metadata content thatwas part of a meta-chunk, such as Ch1. Metadata content differs from ameta-chunk. Metadata content is only part of what a meta-chunkcomprises. Metadata content is associated with the source file (e.g.,file properties, file header information, access control lists, etc.),but does not comprise pointers to payload data in data stream 510. Thepointers can be obtained from the meta-chunk in deduplication appliance380, i.e., the pointers to payload data are not stored at data structure553, though the invention is not so limited.

Thus, the illustrative embodiment features a tiered indexing approachthat minimizes how much data is retained and stored at media agent 344(e.g., in table 553), yet enables media agent to efficiently extractwhat information it needs from deduplication appliance 380. Retainingmetadata content at media agent 344 (e.g., in table 553) enables mediaagent 344 to have fast and local access to important information aboutthe data it backed up to deduplication appliance 380.

FIG. 5B depicts some details of data streams 510, 520, and 530 forgenerating secondary copies 519 to be stored in an example deduplicationappliance 380. FIG. 5B depicts: media agent 344, media agent index 353,communication pathway 376Data to deduplication appliance 380, and datastreams 510, 520, and 530.

Data stream 510 comprises payload data extracted from one or moresources of data, e.g., data files F1 . . . FN. For each data file, mediaagent 344 generates one or more payload data chunks, e.g., F1_Payload1Athrough F1_Payload1M from file F1, FN_PayloadNA through FN_PayloadNXfrom file FN, etc. Media agent 344 transmits the payload data chunks indata stream 510 to deduplication appliance 380.

Data stream 520 comprises meta-chunks. Each meta-chunk comprises:

-   -   (i) metadata content extracted from the backup source (e.g.,        file properties, file header information, access control lists,        etc.), and    -   (ii) one or more pointers to payload data chunks in data stream        510 that belong to the same source (e.g., payload for the same        data file from which the metadata content was extracted, as        depicted by dotted arrows 522.

Thus, for a given source of data, e.g., file F1, metadata stream 520comprises a meta-chunk identified as Ch1 and located at offset Off1 inmetadata stream 520, and the meta-chunk comprises both: (i) metadatacontent extracted from file F1 (e.g., F1_Metadata), and (ii) a pointer(e.g., link_to_Pay1A . . . link_to_Pay1M) to a corresponding payloaddata chunk from file F1 that appears in data stream 510. Likewise, foranother source data file, e.g., file FN, metadata stream 520 comprises ameta-chunk identified as ChN and located at offset OffN in metadatastream 520, and the meta-chunk comprises both: (i) metadata contentextracted from file FN (e.g., FN_Metadata), and (ii) a pointer to acorresponding payload data chunk from file FN (e.g., link_to_PayNA . . .link_to_PayNX). Illustratively, media agent 344 generates only onemeta-chunk per data source, e.g., meta-chunk Ch1 for file F1, but theinvention is not so limited.

Data stream 530 comprises index information pointing to correspondingmeta-chunks in data stream 520, as depicted by dotted arrows 532. Thusfor a given data source, e.g., file F1, an index chunk in index datastream 530 comprises a pointer to a meta-chunk for file F1 that iscarried in data stream 520. For example, a first index chunk in indexdata stream 530 corresponds to source file F1 and points to F1meta-chunk with chunk ID Ch1 at offset Off1 in metadata stream 520.Illustratively, media agent 344 generates only one index chunk per datasource, e.g., file F1, but the invention is not so limited.

After secondary copy 519 is generated and stored at deduplicationappliance 380, subsequent (tertiary) copies are made without passing thebacked up payload data through media agent 344 again. In such scenarios,media agent 344 uses the information it gathered in index 353 (e.g., indata structure 553) to instruct deduplication appliance 380 to make morecopies based on the data stored within the appliance, e.g.,synthetic-full copies, auxiliary copies, etc.—as described in moredetail in other figures herein.

FIG. 6 depicts a logical view of a backup operation in system 300 forgenerating tertiary copies based on a combination of other copies, e.g.,making a synthetic-full copy stored to an example deduplicationappliance. FIG. 6 depicts: media agent 344, media agent index 353, datastreams 620 and 630 using communication pathway 376Data, anddeduplication appliance 380 comprising secondary copies 519A . . . 519Jand synthetic-full copy 629. Logical data flows into media agent 344 aredepicted by two-line unidirectional arrows, indicating that media agent344 retrieves index information and meta-chunks for secondary copies519A . . . 519J. Logical data flows for generating synthetic-full copy629 are depicted by bold unidirectional arrows.

Secondary copies 519A . . . 519J are copies based on primary data thatwere generated in a backup job such as described in FIGS. 5A and 5B.Examples of secondary copies 519 include a full backup copy, anincremental backup copy, and a differential backup copy. Each secondarycopy 519 is stored at deduplication appliance 380. Using these secondarycopies 519 as a source (i.e., not returning to primary data 112), datastorage management system 300 is configured to generate one or moresynthetic-full copies such as synthetic-full copy 629, which is alsostored in deduplication appliance 380 (or in another deduplicationappliance 380).

Synthetic-full copy 629 is generated from a plurality of secondarycopies 519, e.g., 519A . . . 519J. Because it is created from existingsecondary copies and not from primary data, synthetic-full copy 629 issometimes referred to herein as a tertiary copy. Synthetic-full copiesas a concept are well known in the art, i.e., creating a full backupcopy of data at a certain point in time by integrating the most recentdata present in a full backup copy accompanied by one or more subsequentbackup copies (e.g., differential and/or incremental copies).Accordingly a synthetic-full copy is created by manipulating existingsecondary copies without accessing primary data, i.e., within the backupsystem. The synthetic-full copy represents a complete set of data at acertain point in time, which can be further copied and/or archived asneeded.

Although the concept of synthetic-full copies is well known in the art,the method of creating synthetic-full copy 629 through interoperabilitywith deduplication appliance 380 presents novel aspects. See also FIG.12 . By interoperating with deduplication appliance 380, media agent 344avoids many of the traditional data processing operations involved increating a synthetic-full copy, i.e., reading from the full backup copyin storage, reading from the subsequent (e.g., differential,incremental) copies in storage, generating the resultant synthetic-fullcopy, and transmitting the synthetic-full copy to suitable secondarystorage. These traditional operations include not only data manipulationbut also add to network traffic as data is retrieved from secondarystorage, processed by the media agent, and transmitted back to secondarystorage. Even if the synthetic-full copy is not staged (i.e., notarranged in its entirety) at the media agent and is assembled on thefly, the traditional result is that network traffic is increased fromdata traveling to and from the media agent.

However, according to the illustrative embodiments that useinteroperability with deduplication appliance 380, no payload data flowsthrough media agent 344 to generate synthetic-full copies. Instead,media agent 344 retrieves useful indexing information and meta-chunkscreated when secondary copies 519 were initially created, as depicted bythe two-line unidirectional arrows that feed into media agent 344. Mediaagent 344 determines which portions of the source secondary copies 519to include in synthetic-full copy 629, and generates indexinginformation and meta-chunks for the new synthetic-full copy 629, whichare transmitted to deduplication appliance 380 using data streams 620and 630. No payload data travels to/from media agent 344. Data agent 344instructs deduplication appliance 380 on how to use data streams 620 and630 to create synthetic-full copy 629. Instructions are transmitted bydata agent 344 to deduplication appliance 380 (e.g., by usingcommunication pathway 376Cmd not shown in the present figure). In someembodiments, media agent 344 uses “clone” commands to instructdeduplication appliance 380 on which payload data to use forsynthetic-full copy 629 (e.g., by using communication pathway 376Datarather than 376Cmd). Deduplication appliance 380 performs the payloaddata manipulation, adds metadata content, and stores synthetic-full copy629. Deduplication appliance 380 adds deduplication according to its ownnative features without involving media agent 344 in deduplicationoperations.

This lightweight approach substantially lightens the data processingload on the media agent 344 and puts only a minimal load on the datanetwork, because communication pathway 376Cmd and data streams 620 and630 carry relatively little data compared to transmitting payload databetween media agent 344 and deduplication appliance 380. Aftersynthetic-full copy 629 is created, media agent 344 updates index 353 toreflect the presence of a new backup copy (629) in the system. Mediaagent 344 also reports the successful creation of synthetic-full copy629 to storage manager 340.

Data stream 620 is analogous to metadata stream 520. Data stream 620 isa metadata stream that originates at media agent 344 and terminates atdeduplication appliance 380. Data stream 620 comprises one or moremeta-chunks for synthetic-full copy 629, each of which comprises: (i)metadata content to be combined with payload data, and (ii) pointers topayload data chunks stored in deduplication appliance 380 that will beassembled into synthetic-full copy 629.

Data stream 630 is analogous to data stream 530. Data stream 630 is anindex stream that originates at media agent 344 and terminates atdeduplication appliance 380. Data stream 630 comprise one or more indexchunks each of which points to a corresponding meta-chunk in data stream620, as depicted by dotted arrow 532. Index information in data stream630 is also stored by media agent to its associated media agent index353 (e.g., in data structure 553). Optionally, metadata contenttransmitted in metadata stream 620 also is stored therein as discussedin regard to FIG. 5A.

FIG. 7 depicts a logical view of a backup operation in system 300 forgenerating tertiary copies based on other copies, e.g., making anauxiliary copy stored to an example deduplication appliance 380. FIG. 7depicts: media agent 344, media agent index 353, data streams 720 and730 using communication pathway 376Data, and deduplication appliance 380comprising secondary copy 519 and auxiliary copy 729. Logical data flowsinto media agent 344 are depicted by two-line unidirectional arrows,indicating that media agent 344 retrieves information for secondarycopies 519A . . . 519J. Logical data flows for generating auxiliary copy729 are depicted by bold unidirectional arrows.

Secondary copy 519 is a copy based on primary data that was generated ina backup job such as described in FIGS. 5A and 5B. Notably, Auxiliarycopies can be created from any pre-existing copy, whether a secondarycopy 519 or a synthetic-full copy 629, or another auxiliary copy729/829, without limitation.

Auxiliary copy 729 is generated from secondary copy 519. Auxiliary copy729 is a copy of a copy. Because it is created from an existing copy andnot from primary data, auxiliary copy 729 is sometimes referred toherein as a tertiary copy. Each secondary copy 519 is stored atdeduplication appliance 380. Using secondary copy 519 (or another copy)as a source (i.e., not returning to primary data 112), data storagemanagement system 300 is configured to generate one or more auxiliarycopies such as auxiliary copy 729, which is also stored in deduplicationappliance 380 (or auxiliary copy 829 stored to another deduplicationappliance 380 as shown in FIG. 8 ). Auxiliary copies as a concept arewell known in the art, i.e., creating a copy from a pre-existing copy.Auxiliary copies provide additional standby copies of data and mayreside on different secondary storage devices than the initial secondarycopies (see, e.g., FIG. 8 ).

Although the concept of auxiliary copies is well known in the art, themethod of creating auxiliary copy 729 through interoperability with oneor more deduplication appliances 380 presents novel aspects (see alsoFIGS. 8, 12 ). By interoperating with deduplication appliance 380, mediaagent 344 avoids some of the traditional data processing tasks involvedin creating auxiliary copies, such as reading in the source copy fromstorage and transmitting the auxiliary copy to suitable secondarystorage. Even if the auxiliary copy is not staged (i.e., not arranged inits entirety) at the media agent, the auxiliary copy operation creatednetwork traffic to and from the media agent.

However, according to the illustrative embodiments that useinteroperability with deduplication appliance 380, no payload data flowsthrough media agent 344 to generate auxiliary copies. Instead, mediaagent 344 retrieves useful information about the source copy, e.g.,about secondary copy 519, as depicted by the two-line unidirectionalarrows that feed into media agent 344. For example, media agent 344retrieves a file ID from index 353, which points it to a meta-chunk IDstored at deduplication appliance 380 (see, e.g., data stream 520).Media agent 344 then retrieves the appropriate meta-chunk (e.g., Ch1)from deduplication appliance 380. Now, media agent 344 has the file ID,metadata content, and pointers to payload data chunks at deduplicationappliance—collectively enough information to instruct deduplicationappliance 380 in how to create auxiliary copy 729 from secondary copy519. Media agent 344 generates indexing information and meta-chunks forthe new auxiliary copy 729, which are transmitted to deduplicationappliance 380 using data streams 720 and 730. No payload data travelsto/from media agent 344. In contrast to the information needed forcreating synthetic-full copy 629 (see FIG. 6 ), auxiliary copy 629requires less granularity here, because all of the source copy is copiedto make the auxiliary copy. Thus, the file ID is enough to initiate theauxiliary copy process here.

Illustratively metadata content for the auxiliary copy is supplied bymedia agent 344 from its index 353 (see, e.g., table 553) or,alternatively, from the meta-chunks it retrieves from deduplicationappliance 380. In some embodiments, no metadata content flows throughmedia agent 344 for generating auxiliary copies, because deduplicationappliance 380 retrieves it from its own storage without involving mediaagent 344. Data agent 344 instructs deduplication appliance 380 on howto use data streams 720 and 730 to create auxiliary copy 729.Instructions are transmitted by data agent 344 to deduplicationappliance 380 (e.g., by using communication pathway 376Cmd not shown inthe present figure). In some embodiments, media agent 344 uses “copy”commands to instruct deduplication appliance 380 on which payload datato use for synthetic-full copy 629. Deduplication appliance 380 performsthe payload data manipulation, adds metadata content, and storesauxiliary copy 729. Deduplication appliance 380 adds deduplicationaccording to its own native features without involving media agent 344in deduplication operations.

This lightweight approach substantially lightens the data processingload on the media agent 344 and puts only a minimal load on the datanetwork, because communication pathway 376Cmd and data streams 720 and730 carry relatively little data compared to transmitting payload databetween media agent 344 and deduplication appliance 380. After auxiliarycopy 729 is created, media agent 344 updates index 353 to reflect thepresence of a new backup copy (729) in the system. Media agent 344 alsoreports the successful creation of auxiliary copy 729 to storage manager340.

Data stream 720 is analogous to metadata stream 620. Data stream 720 isa metadata stream that originates at media agent 344 and terminates atdeduplication appliance 380. Data stream 720 comprises one or moremeta-chunks for auxiliary copy 729, each of which comprises: (i)metadata content to be combined with payload data, and (ii) pointers topayload data chunks stored in deduplication appliance 380 that will becopied to auxiliary copy 729.

Data stream 730 is analogous to data stream 630. Data stream 730 is anindex stream that originates at media agent 344 and terminates atdeduplication appliance 380. Data stream 730 comprises one or more indexchunks each of which points to a corresponding meta-chunk in data stream720, as depicted by dotted arrow 532. Index information in data stream730 is also stored by media agent 344 to its associated media agentindex 353 (e.g., in data structure 553). Optionally, metadata contenttransmitted in metadata stream 720 also is stored therein as discussedin regard to FIG. 5A. A scenario that makes an auxiliary copy from asource copy on another deduplication appliance is described in the nextfigure.

FIG. 8 depicts a logical view of a backup operation in system 300 forgenerating tertiary copies across deduplication appliances, e.g., makingan auxiliary copy 829 from a copy on a first deduplication appliance380-1 to a second deduplication appliance 380-2. FIG. 8 depicts: mediaagent 344, media agent index 353, deduplication appliance 380-1comprising secondary copy 519, deduplication appliance 380-2 comprisingauxiliary copy 829; and data streams 720, 730, and 890. Media agent 344uses communication pathway 376Cmd for instructions and responses to/fromdeduplication appliance 380-2.

The operations in this figure are similar to what is depicted in FIG. 7except that: (i) Payload data from secondary copy 519 to auxiliary copy829 is carried by communication pathway 890 between deduplicationappliance 380-1 and 380-2; it does not pass through media agent 344; and(ii) auxiliary copy 829 resides in deduplication appliance 380-2 whichis different from deduplication appliance 380-1 that stores the sourcesecondary copy 519. No payload data flows through media agent 344 togenerate auxiliary copies from one deduplication appliance to another.

Data streams 720 and 730 were described in more detail in FIG. 7 . Here,they originate at data agent 344 and terminate at deduplicationappliance 380-2. Data streams 720 and 730 comprise information retrievedby data agent 344 from its associated index 353 and from deduplicationappliance 380-1 as shown by the two-line unidirectional arrows that feedinto media agent 344. These were described in more detail in FIG. 7 .

Data stream 890 is generated and transmitted by deduplication appliance380-1 and received and processed by deduplication appliance 380-2, thusoffloading media agent 344 from handling payload data.

Although the present figure depicts making an auxiliary copy at a seconddeduplication appliance from a source at a first deduplicationappliance, similar logic applies for making synthetic-full copies. Insuch a scenario, source backup copies 519A . . . 519J are stored atdeduplication appliance 380-1 and synthetic-full copy 629 is stored todeduplication appliance 380-2, wherein the payload for synthetic-fullcopy 629 is carried by pathway 890 from one appliance to another withoutpassing through media agent 344.

FIG. 9 depicts a logical view of a recovery operation in system 300 forrestoring primary data from secondary/tertiary copies stored in anexample deduplication appliance 380. FIG. 9 depicts: application/filesystem 110, restored primary data 112, data agent 142, media agent 344,media agent index 353, and data streams 910 and 920 and 970. See alsoFIG. 13 . Source secondary copy 519 is not shown in the present figure,but see FIG. 5A. Collectively, data streams 910 and 920 are received bymedia agent 344 from deduplication appliance 380 via communicationpathway 376Data. Logically, FIG. 9 reverses the flow of data depicted inFIGS. 5A and 5B when secondary copy 519 was initially made and which isnow being restored. Tertiary copies such as 629, 729, and/or 829 arerestored in like fashion. Logical data flows for restoring copy 519 aredepicted by bold unidirectional arrows.

Dotted arrow 532 indicates that pointers in index 353 provide mediaagent 344 with information to retrieve meta-chunks from deduplicationappliance 380 using metadata stream 920. From the retrieved meta-chunks,media agent 344 retrieves pointers to corresponding payload data storedin deduplication appliance as depicted by dotted arrows 522. The payloaddata chunks are retrieved using data stream 910.

Data stream 910 is analogous to data stream 510 and comprises payloaddata that was originally stored to deduplication appliance 380 whensecondary copy 519 was created. Data stream 910 originates atdeduplication appliance 380 and terminates at media agent 344.

Data stream 920 originates at deduplication appliance 380 and terminatesat media agent 344. Data stream 920 is analogous to data stream 520 andcomprises meta-chunks that comprise: (i) metadata content of secondarycopy 519, and (ii) pointers to payload data stored at deduplicationappliance 380, as depicted by dotted arrows 522. Illustratively, mediaagent 344 uses index 353 (e.g., data structure 553) to identifymeta-chunks associated with the copy to be restored, e.g., 519, and asshown by dotted arrow 532, uses that information to instructdeduplication appliance 380 to provide the meta-chunks in data stream920. In turn, the pointers in meta-chunks of data stream 920 are used toidentify payload data for secondary copy 519 as depicted by arrows 522.Data agent 344 instructs deduplication appliance to transmit thosepayload data using data stream 910. Illustratively metadata content forthe restored copy is retrieved from index 353 and/or from themeta-chunk(s) in data stream 920.

Deduplication appliance 380 applies its native features as appropriate,e.g., rehydrating deduplicated data, decompressing compressed data,decrypting encrypted data before generating data streams 910 and 920.

Data stream 970 is analogous to data stream 170 and/or data stream 171described in more detail in FIGS. 1F and 1G. Data stream 970 isconfigured with interleaved metadata and payload data according to atraditional format employed by prior art data storage managementsystems. Data stream 970 is formed by media agent 344 from segregateddata received in data streams 910 and 920 and/or metadata contentretrieved from index 353. Data stream 970 is transmitted to data agent142, which in turn “deposits” the restored data to primary storage inthe form of native format (primary) data 112. An application or filesystem 110 directly accesses and consumes the restored primary data 112.Data agent 142 thus lacks awareness of how the data was transmitted tomedia agent 344 and simply receives a traditionally-formatted datastream 970.

FIG. 10 depicts a method 1000 in system 300 for generating secondarycopies based on primary data by segregating payload, metadata, and indexinformation into separate data streams, according to an illustrativeembodiment of the present invention. Media agent 344 performs theoperations of method 1000, except as otherwise noted. See also FIGS.3B-5B.

At block 1002, storage manager 340 triggers a backup job (or informationmanagement job, or storage operation job) based on a storage policy thatincludes deduplication appliance 380 as a storage destination forsecondary copies (e.g., 519). Illustratively management database 346 iswhere storage policies are stored in system 300. Based on a storagepolicy (e.g., 148), storage manager 340 initiates a backup job byinstructing data agent 142 and media agent 344 to generate a backup copyfrom a certain data source and to store the backup copy to the specifieddestination, e.g., deduplication appliance 380. A backup copy can be asecondary copy based on primary data or a tertiary copy based on apre-existing copy. The present figure generally describes how secondarycopies are generated and stored to deduplication appliance 380. Tertiarycopies are discussed in more detail in FIGS. 6-8 and 12 .

At block 1004, for a copy based on primary data (e.g., full,incremental, differential copies) media agent 344 processes metadata andpayload to generate a plurality of data chunks. From the plurality ofdata chunks, media agent 344 generates separate data streams todeduplication appliance 380 by segregating payload data from itsmetadata from index. More details are given in another figure. See alsoFIGS. 5A and 5B.

At block 1006, media agent 344 instructs deduplication appliance 380 toapply deduplication to a first (“payload”) data stream comprisingpayload data (e.g., 510). Instructions are illustratively transmittedusing an Application Programming Interface (“API”) over a commandchannel such as communication pathway 376Cmd. See also FIG. 4 .

At block 1008, media agent 344 instructs deduplication appliance 380 topass-through to storage a second (“metadata”) data stream (e.g., 520)and a third (“index”) data stream (e.g., 530), i.e., to store thereceived data without applying deduplication. Instructions areillustratively transmitted using an Application Programming Interface(“API”) over a command channel such as communication pathway 376Cmd. Seealso FIG. 4 .

In some embodiments, data streams 510, 520, and 530 operateconcurrently. In other embodiments the data streams are transmittedsequentially from media agent 344 to deduplication appliance 380, e.g.,510, 520, and 530. In some embodiments, instructions also include alocation or other identifier for where deduplication appliance 380should store the secondary copy being created based on data streams 510,520, and 530. In other embodiments, deduplication appliance 380 picks asuitable location and reports it to media agent 344.

At block 1010, deduplication appliance 380 stores contents of the second(metadata) data stream 520 (i.e., meta-chunks) and third (index) datastream 530 in pass-through mode without attempting to deduplicate.Deduplication appliance 380 applies deduplication to payload data in thefirst (payload) data stream 510; and stores the resulting data to one ormore of its local storage devices (e.g., 390). See also FIG. 4 .Deduplication is applied by deduplication appliance 380 according to itsown native logic and feature capabilities. The data is stored bydeduplication appliance 380 using its own native logic and featurecapabilities, and responsive to instructions received from media agent344. Transaction confirmation(s) are sent back to media agent 344 usingthe API. See also FIGS. 4, 5A, and 5B.

At block 1012, media agent 344 receives transaction confirmation(s)and/or suitable reporting information, such as data size, storagelocation, timestamps, etc., from deduplication appliance 380. Mediaagent 344 updates associated media agent index 353 (e.g., adding atimestamp and a location for secondary copy 519), and transmits jobstatus information to storage manager 340. At this point, one or moresecondary copies 519 have been created, appropriately deduplicated, andstored to deduplication appliance 380. Secondary copies 519 are trackedby media agent 344 in its associated index 353 and in some embodimentsare storage manager 340 tracks them in its management database 346.

FIG. 11 depicts some salient operations in block 1004 of method 1000.This block is directed to: for a copy based on primary data (e.g., full,incremental, differential copies) media agent 344 processes metadata andpayload and generates separate data streams to deduplication applianceby segregating payload data from its metadata from index Some salientoperations are described below. See also FIGS. 5A and 5B.

At block 1101, media agent 344 receives payload and metadata of thesource file(s) in a data stream (e.g., 170/171) transmitted by a data142 that is specially configured to back up the source data. Media agent344 processes the received metadata and payload data, and generatesindex information for its associated media agent index 353. See, e.g.,table 553.

At block 1102, media agent 344 generates data chunks from processedpayload, metadata content, pointers, and index information, wherein eachgenerated data chunk comprises payload data or metadata content or indexinformation.

At block 1106, media agent 344 generates a first (“payload”) data stream(e.g., 510) comprising only “payload data chunks” from the generateddata chunks. The payload data for these payload data chunks wasextracted by media agent 344 from the source data being backed up, e.g.,from a data stream 170/171 received from data agent 142.

At block 1108, media agent 344 generates a second (“metadata”) datastream (e.g., 520) comprising meta-chunks. Metadata content from thesource data and pointers to the payload data chunks in data stream 510are included in each meta-chunk in data stream 520. See also FIGS. 5Aand 5B and accompanying text.

At block 1110, media agent 344 generates a third (“index”) data stream(e.g., 530) comprising “index chunks.” Each index chunk comprises indexinformation such as a pointer to a corresponding meta-chunk used inmetadata stream 520, e.g., offset, meta-chunk id, etc. See also table553 and accompanying text. Thus, each index chunk points to acorresponding meta-chunk, which in turn points to payload data chunks.Indexing information in the index chunks and metadata content are storedto index 353, thus preserving in media agent 344 information forstreamlined and granular access to data stored at deduplicationappliance 380. See also FIGS. 5A and 5B and accompanying text.

FIG. 12 depicts a method 1200 in system 300 for generating tertiarycopies based on other copies, according to an illustrative embodiment ofthe present invention. Media agent 344 performs the operations of method1200, except where otherwise noted. See also FIGS. 6, 7, and 8 .

At block 1202, storage manager 340 triggers a backup job (or informationmanagement job, or storage operation job) based on a storage policy thatincludes deduplication appliance 380 as a storage destination fortertiary copies (e.g., 629, 729, 829). Illustratively managementdatabase 346 is where storage policies are stored in system 300. Basedon a storage policy (e.g., 148), storage manager 340 initiates a backupjob by instructing media agent 344 to generate a tertiary copy from oneor more secondary copy sources (e.g., 519) or from other copies and tostore the resulting tertiary copy to deduplication appliance 380. Thepresent figure generally describes how tertiary copies are generated andstored to one or more deduplication appliances 380.

At block 1204, which is a decision point, media agent 344 determineswhether the tertiary copy to be made is of a kind for which granularityof the source data is needed. For example, for auxiliary copies, whichare complete copies of pre-existing copies, no granularity is neededsince the entire set of data chunks belonging to the source copy arecopied to the tertiary copy in a substantially linear fashion based on afile ID obtained from storage manager 340 and/or index 353. In such acase, control passes to block 1210. For example, for synthetic-fullcopies, data chunk granularity (or even sub-chunk granularity) is neededto find and properly integrate the latest data from multiple sourcecopies into the synthetic-full copy. In such a case, control passes toblock 1206.

At block 1206, for a synthetic-full copy (which is generated from one ormore full, incremental, and/or differential copies) media agent 344 usesindex information & meta-chunks of source files to generate metadatastream 620 and index stream 630 for the synthetic-full copy, includingdetermining which portions of source files to include in thesynthetic-full copy. See also FIG. 6 and accompanying text.

The illustrative synthetic-full copy 629 is formed by integrating themost recently created/changed data chunks found in the plurality ofsource secondary copies 519. Hence the need for chunk granularity withinthe source secondary copies 519. Notably, these secondary copies 519 arestored at deduplication appliance 380 in deduplicated format that isnatively supplied and managed by the appliance. In some embodiments,granularity is finer than the chunk level, e.g., data blocks, dataextents, but the same process applies. Only the most recent data fromthe source files are identified by media agent 344 and referenced ininstructions to deduplication appliance 380. Media agent 344 transmitsboth index information (stream 630) and meta-chunks (stream 620) todeduplication appliance 380 with instructions to find correspondingpayload data chunks and integrate them into synthetic-full copy 629along with appropriate metadata content. See also FIG. 6 andaccompanying text.

At block 1208, media agent 344 instructs deduplication appliance 380 togenerate and store synthetic-full copy 629 based on payload data pointedto by metadata stream 620 and using metadata content from metadatastream 620 as identified by index stream 630. See also FIG. 6 andaccompanying text. No payload data passes through and/or plays back atmedia agent 344, which is one of the advantageous aspects ofinteroperability with deduplication appliance 380 according to thepresent invention. Control passes to block 1213.

Block 1210 is reached from block 1204. For an auxiliary copy (e.g.,729/829), media agent 344 uses a file ID and metadata chunks of thesource file (e.g., 519) to generate metadata stream 720 and index stream730 for the resultant auxiliary copy 729/829. See also FIGS. 7 and 8 andaccompanying text.

At block 1212, media agent 344 instructs deduplication appliance 380 togenerate and store auxiliary copy 729/829 by copying payload data aspointed to by metadata stream 720 and using metadata content frommetadata stream 720. In some other embodiments (see, e.g., FIG. 8 ),media agent 344 extracts meta-chunks from a first deduplicationappliance, e.g., 380-1, and transmits the meta-chunks to a seconddeduplication appliance, e.g., 380-2, with instructions to copy thepayload data chunks from the first deduplication appliance 380-1 andgenerate and store auxiliary copy 829. In all the auxiliary copyscenarios, no payload data passes through and/or plays back at mediaagent 344, which is one of the advantageous aspects of interoperabilitywith deduplication appliance 380 according to the present invention. Seealso FIGS. 7 and 8 and accompanying text. Control passes to block 1213.

At block 1213, which is reached from block 1208 and from block 1212,deduplication appliance 380 handles compression, encryption, and/ordeduplication of resultant tertiary copy 629/729/829 using theappliance's native features. Deduplication appliance 380 illustrativelystores tertiary copy 629/729/829 within its data storage devices 390 andtransmits transaction confirmation(s) to media agent 344 using the APIover communication pathway 376Cmd. In some embodiments, deduplicationappliance 380 transmits synthetic-full copy 629 to another deduplicationappliance 380.

At block 1214, media agent 344 receives transaction confirmation fortertiary copy 629/729/829 from deduplication appliance 380. Media agent344 updates index 353 to track the new tertiary copy, and reports backupjob status and tertiary copy information to storage manager 340.

FIG. 13 depicts a method 1300 in system 300 for restoring primary datafrom secondary/tertiary copies stored in an example deduplicationappliance 380, according to an illustrative embodiment of the presentinvention. Method 1300 is performed by media agent 344 except whereexpressly stated otherwise. See also FIG. 9 and accompanying text.

At block 1302, media agent 344 receives instructions to restore datastored at deduplication appliance 380 (e.g., 519, 629, 729, 829) to aclient computing device 102. Illustratively, instructions are receivedfrom storage manager 340, which in turn receives restore request(s) viaa user interface, such as via an administration console or via a dataagent interface at client computing device 102. Requests to restore dataare well known in the art.

At block 1304, media agent 344 uses its associated media agent index 353(e.g., data structure 553) to identify meta-chunks at deduplicationappliance 380 that are needed for restoring the requested data (e.g.,file F1). Illustratively, table 553 indicates that file F1 is associatedwith meta-chunk Ch1, which is to be found at offset location Off1—see,e.g., FIG. 5B.

At block 1306, media agent 344 instructs deduplication appliance 380 totransmit the identified meta-chunks (e.g., Ch1) and payload data pointedto by the identified meta-chunks (e.g., F1_Payload1A . . .F1_Payload1M), which may require deduplication appliance 380 torehydrate/decrypt/decompress data before transmitting to media agent344. Media agent 344 receives data stream 920, parses the meta-chunks tofind pointers to payload data, and requests the payload data, whicharrives in payload data stream 910 from deduplication appliance 380.Deduplication appliance 380 illustratively uses its own native logic andfeature capabilities to automatically rehydrate payload data belongingto a deduplicated copy, without needing media agent 344 to instruct iton rehydration, though the present invention is not so limited.

At block 1308, media agent 344 in conjunction with data agent 142process recovered payload data and corresponding metadata content togenerate a restored copy of data as recovered from deduplicationappliance 380. Illustratively, media agent 344 takes metadata contentand payload data and generates an interleaved data stream (e.g., 970)that it transmits to data agent 142. Data agent 142 processes thereceived data stream 970 and installs the restored copy as primary data112 at client computing device 102. At this point, the applicationand/or file system 110 that consumes this data can natively access it.

At block 1310, media agent 344 updates media agent index 353 and reportsthe restore status to storage manager 340.

In regard to the figures described herein, other embodiments arepossible within the scope of the present invention, such that theabove-recited components, steps, blocks, operations, messages, requests,queries, and/or instructions are differently arranged, sequenced,sub-divided, organized, and/or combined. In some embodiments, adifferent component may initiate or execute a given operation. Forexample, in some embodiments, media agent 344 triggers backup and/orrestore jobs without instructions from storage manager 340. In someembodiments, media agent 344 receives metadata and status/performancereporting from deduplication appliance 380 that media agent 344incorporates into index 353 and/or reports to storage manager 340. Theselatter features largely depend upon the feature capabilities of APIto/from deduplication appliance 380.

EXAMPLE EMBODIMENTS

Some example enumerated embodiments of the present invention are recitedin this section in the form of methods, systems, and non-transitorycomputer-readable media, without limitation.

According to an example embodiment, a method comprises by a media agentthat executes on a first computing device comprising one or moreprocessors and computer memory, during a backup job for primary datathat results in one or more secondary copies, generating a plurality ofdata chunks, wherein the media agent configures each data chunk tocomprise: (i) payload data, or (ii) metadata, or (iii) indexinformation; by the media agent, generating a first data streamtransmitted to an appliance that comprises one or more data storagedevices and that also is capable of self-managed deduplication, whereinthe first data stream comprises first data chunks and does not comprisesecond data chunks and third data chunks, and wherein each first datachunk comprises payload data based on the primary data being backed upin the backup job; by the media agent, generating a second data streamtransmitted to the appliance, wherein the second data stream comprisessecond data chunks and does not comprise first data chunks and thirddata chunks, wherein each second data chunk comprises metadata for theprimary data being backed up and further wherein each second data chunkpoints to one or more first data chunks in the first data stream; by themedia agent, generating a third data stream transmitted to theappliance, wherein the third data stream comprises third data chunks anddoes not comprise first data chunks and second data chunks, wherein eachthird data chunk points to a corresponding second data chunk in thesecond data stream.

The above-recited method further comprises: by the media agent,instructing the appliance to apply deduplication to the first datachunks in the first data stream; by the media agent, instructing theappliance not to apply deduplication to the second data chunks in thesecond data stream and to the third data chunks in the third datastream; and by the media agent, instructing the appliance to store theone or more secondary copies resulting from the metadata in the seconddata chunks and from the payload data in the first data chunks to theone or more data storage devices in the appliance. The above-recitedmethod wherein the one or more secondary copies are stored at theappliance in deduplicated form, and wherein during the backup job themedia agent does not deduplicate the first data stream, the second datastream, and the third data stream. The above-recited method furthercomprises: by the media agent, storing to an associated index at thefirst computing device: contents of the third data chunks which point tocorresponding second data chunks in the second data stream, and metadatafor the primary data from the second data chunks. The above-recitedmethod further comprises: By the media agent, updating an associatedindex at the first computing device with at least one of: (a) storageresults reported to the media agent by the appliance, and (b) for eachof the one or more secondary copies a corresponding storage locationwithin the appliance. The above-recited method wherein based ondetermining that the appliance is capable of deduplication, the mediaagent generates the first data stream, the second data stream, and thethird data stream, and instructs the appliance to apply deduplication tothe first data chunks, and further instructs the appliance to storewithout deduplication the second data chunks and the third data chunks.The above-recited method wherein a given second data chunk includes anoffset of the corresponding first data chunk within the first datastream. The above-recited method wherein a given third data chunkincludes an offset of the corresponding second data chunk within thesecond data stream. The above-recited method wherein the media agentinstructs the appliance where to store the one or more secondary copieswithin the one or more storage devices in the appliance; and wherein theindex associated with the media agent includes for each of the one ormore secondary copies a corresponding storage location within theappliance. The above-recited method wherein a storage manager instructsthe media agent and a first data agent to process the primary data beingbacked up in the backup job for further processing by and storage at theappliance as the one or more secondary copies. The above-recited methodwherein based on a first storage policy, a storage manager instructs themedia agent and a first data agent to process the primary data beingbacked up in the backup job for further processing by and storage at theappliance as the one or more secondary copies. The above-recited methodwherein based on a first storage policy, a storage manager instructs themedia agent to process the primary data being backed up in the backupjob for further processing by and storage at the appliance as the one ormore secondary copies; and wherein the storage manager indicates to themedia agent that the appliance is capable of deduplication and storageof the one or more secondary copies. The above-recited method wherein astorage manager instructs the media agent to generate the first, second,and third data stream, and further to transmit the first data stream tothe appliance with instructions to deduplicate the first data chunkstherein. The above-recited method wherein based on a first storagepolicy, a storage manager instructs the media agent to generate thefirst, second, and third data stream, and further to transmit the firstdata stream to the appliance with instructions to deduplicate the firstdata chunks therein. The above-recited method wherein based on a firststorage policy, a storage manager instructs the media agent to back upthe primary data to the appliance, and further wherein: based ondetermining that the appliance is capable of deduplication, the mediaagent generates the first data stream, the second data stream, and thethird data stream, and instructs the appliance to apply deduplication tothe first data chunks in the first data stream, and further instructsthe appliance to store without deduplication the second data chunks inthe second data stream and the third data chunks in the third datastream. The above-recited method wherein the media agent co-resides onthe first computing device with a first data agent that accesses theprimary data being backed up in the backup job; and wherein the firstdata agent in conjunction with the media agent process the primary databeing backed up in the backup job for deduplication by and storage atthe appliance as the one or more secondary copies. The above-recitedmethod wherein the media agent co-resides on the first computing devicewith a first data agent that accesses the primary data being backed upin the backup job; and wherein the first data agent in conjunction withthe media agent process the primary data being backed up in the backupjob for deduplication by and storage at the appliance as the one or moresecondary copies; and wherein an index associated with the media agenttracks the one or more secondary copies stored at the appliance.

A data storage management system (e.g., system 300) that performs theabove-recited methods.

A non-transitory computer readable medium storing instructions, whichwhen executed by at least one computing device (e.g., media agent 344),perform the above-recited methods.

According to another example embodiment, a method for using an applianceto generate and store tertiary copies based on secondary copies, themethod comprises: by a media agent that executes on a first computingdevice comprising one or more processors and computer memory, receivinginstructions from a storage manager to generate a synthetic-full copyfrom a plurality of secondary copies that are stored in an appliance incommunication with the media agent, wherein the appliance comprises oneor more data storage devices and is capable of self-manageddeduplication; by the media agent, extracting from an associated indexat the first computing device information about the plurality ofsecondary copies, wherein the information comprises pointers to aplurality of second data chunks stored without deduplication at theappliance, wherein a given second data chunk comprises metadata for acorresponding secondary copy among the plurality of secondary copies,and further comprises pointers to one or more first data chunks storedwith deduplication at the appliance, and wherein a given first datachunk comprises payload data of the corresponding secondary copy amongthe plurality of secondary copies; by the media agent, determining whichfirst data chunks and which metadata from the second data chunks to beincluded in the synthetic-full copy; by the media agent, generating afirst data stream transmitted to the appliance, wherein the first datastream comprises a third data chunk comprising the metadata from thesecond data chunks determined by the media agent to be included in thesynthetic-full copy, and further comprises pointers to one or more firstdata chunks determined by the media agent to be included in thesynthetic-full copy; by the media agent, generating a second data streamtransmitted to the appliance, wherein the second data stream comprises afourth data chunk comprising a pointer to a corresponding third datachunk in the first data stream; by the media agent, instructing theappliance to generate and store the synthetic-full copy based on payloaddata in the one or more first data chunks and further based on themetadata in the third data chunk; and wherein the synthetic-full copy isgenerated and stored at the appliance without passing payload datathrough the media agent.

The above-recited method wherein at least some of the plurality ofsecondary copies are stored at the appliance in deduplicated form. Theabove-recited method wherein the secondary copies and the synthetic-fullcopy are stored at the appliance in deduplicated form. The above-recitedmethod wherein the media agent instructs the appliance to applydeduplication to the payload data in the one or more first data chunks,and further instructs the appliance not to apply deduplication to thefirst data stream and to the second data stream. The above-recitedmethod wherein the synthetic-full copy is stored at the appliance indeduplicated form based on the media agent instructing the appliance toapply deduplication to the payload data in the one or more first datachunks, and further instructing the appliance not to apply deduplicationto the first data stream and to the second data stream. Theabove-recited method wherein the synthetic-full copy is stored at theappliance in deduplicated form, and further wherein no deduplication isapplied by the media agent to the first data stream and the second datastream. The above-recited method further comprises: by the media agent,instructing the appliance to store the synthetic-full copy to the one ormore data storage devices in the appliance. The above-recited methodfurther comprises: by the media agent, instructing the appliance tostore the synthetic-full copy to the one or more data storage devices inthe appliance; and by the media agent, updating an associated index totrack the synthetic-full copy stored at the appliance.

A data storage management system that performs the above-recitedmethods.

A non-transitory computer readable medium storing instructions, whichwhen executed by at least one computing device, perform theabove-recited methods.

According to yet another example embodiment, a method for using anappliance to generate and store tertiary copies based on secondarycopies, the method comprises: by a media agent that executes on a firstcomputing device comprising one or more processors and computer memory,receiving instructions from a storage manager to generate an auxiliarycopy from a secondary copy that is stored in an appliance incommunication with the media agent, wherein the appliance comprises oneor more data storage devices and is capable of self-manageddeduplication; by the media agent, extracting from an associated indexat the first computing device a storage location of the secondary copyin the appliance, wherein a second data chunk at the storage locationcomprises metadata for the secondary copy, and further comprisespointers to one or more first data chunks stored with deduplication atthe appliance, and wherein a given first data chunk comprises payloaddata of the secondary copy; by the media agent, determining that the oneor more first data chunks and the metadata from the second data chunkare to be copied to the auxiliary copy; by the media agent, generating afirst data stream transmitted to the appliance, wherein the first datastream comprises a third data chunk comprising the metadata from thesecond data chunk, and further comprises pointers to the one or morefirst data chunks; by the media agent, generating a second data streamtransmitted to the appliance, wherein the second data stream comprises afourth data chunk comprising a pointer to the third data chunk in thefirst data stream; by the media agent, instructing the appliance togenerate and store the auxiliary copy based on payload data in the oneor more first data chunks and further based on the metadata in the thirddata chunk; and wherein the auxiliary copy is generated and stored atthe appliance without passing payload data through the media agent.

The above-recited method wherein the secondary copy and the auxiliarycopy are stored at the appliance in deduplicated form. The above-recitedmethod wherein the media agent instructs the appliance to applydeduplication to the payload data in the one or more first data chunks,and further instructs the appliance not to apply deduplication to thefirst data stream and to the second data stream. The above-recitedmethod wherein the auxiliary copy is stored at the appliance indeduplicated form based on the media agent instructing the appliance toapply deduplication to the payload data in the one or more first datachunks, and further instructing the appliance not to apply deduplicationto the first data stream and to the second data stream. Theabove-recited method wherein the auxiliary copy is stored at theappliance in deduplicated form, and further wherein no deduplication isapplied by the media agent to the first data stream and the second datastream. The above-recited method further comprises: by the media agent,instructing the appliance to store the auxiliary copy to the one or moredata storage devices in the appliance. The above-recited method furthercomprises: by the media agent, instructing the appliance to store theauxiliary copy to the one or more data storage devices in the appliance;and by the media agent, updating an associated index to track theauxiliary copy stored at the appliance. The above-recited method furthercomprises: by the media agent, instructing the appliance to transmit theauxiliary copy to a second appliance also in communication with themedia agent; by the media agent, instructing the second appliance tostore the auxiliary copy; and by the media agent, updating an associatedindex to track the auxiliary copy stored at the second appliance; andwherein no second data chunks that are part of the secondary copy flowthrough the media agent to generate or store the auxiliary copy.

A data storage management system that performs the above-recitedmethods.

A non-transitory computer readable medium storing instructions, whichwhen executed by at least one computing device, perform theabove-recited methods.

According to another illustrative embodiment, a method for restoringdeduplicated secondary copies from an appliance, the method comprises:by a media agent that executes on a first computing device comprisingone or more processors and computer memory, receiving instructions froma storage manager to restore a secondary copy from an appliance incommunication with the media agent, wherein the appliance deduplicatedthe secondary copy when storing it; by the media agent, extracting froman associated index at the first computing device information about thesecondary copy, wherein the information comprises pointers to a seconddata chunk stored without deduplication at the appliance, wherein thesecond data chunk comprises metadata for the secondary copy and furthercomprises pointers to one or more first data chunks stored withdeduplication at the appliance, and wherein a given first data chunkcomprises payload data of the secondary copy; by the media agent,causing a first data stream from the appliance to transmit to the mediaagent, wherein the first data stream comprises the second data chunk; bythe media agent, causing a second data stream from the appliance totransmit to the media agent, wherein the second data stream comprisesthe one or more first data chunks pointed to by the pointers in thesecond data chunk, wherein the appliance rehydrates at least some of thefirst data chunks before transmitting to the media agent; by the mediaagent processing the first data chunks and the metadata in the seconddata chunk to generate a third data stream transmitted to a data agentfor restoring the secondary copy to primary data.

The above-recited method wherein the third data stream interleavesportions of the metadata and portions of the payload from the first datachunks. The above-recited method further comprises: by the media agent,transmitting the third data stream to the data agent that transformsdata in the third data stream into primary data accessible to anapplication that executes on the first computing device.

A data storage management system that performs the above-recitedmethods.

A non-transitory computer readable medium storing instructions, whichwhen executed by at least one computing device, perform theabove-recited methods.

In other embodiments, a system or systems may operate according to oneor more of the methods and/or computer-readable media recited in thepreceding paragraphs. In yet other embodiments, a method or methods mayoperate according to one or more of the systems and/or computer-readablemedia recited in the preceding paragraphs. In yet more embodiments, acomputer-readable medium or media, excluding transitory propagatingsignals, may cause one or more computing devices having one or moreprocessors and non-transitory computer-readable memory to operateaccording to one or more of the systems and/or methods recited in thepreceding paragraphs.

Terminology

Conditional language, such as, among others, “can,” “could,” “might,” or“may,” unless specifically stated otherwise, or otherwise understoodwithin the context as used, is generally intended to convey that certainembodiments include, while other embodiments do not include, certainfeatures, elements and/or steps. Thus, such conditional language is notgenerally intended to imply that features, elements and/or steps are inany way required for one or more embodiments or that one or moreembodiments necessarily include logic for deciding, with or without userinput or prompting, whether these features, elements and/or steps areincluded or are to be performed in any particular embodiment.

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense, as opposed to anexclusive or exhaustive sense, i.e., in the sense of “including, but notlimited to.” As used herein, the terms “connected,” “coupled,” or anyvariant thereof means any connection or coupling, either direct orindirect, between two or more elements; the coupling or connectionbetween the elements can be physical, logical, or a combination thereof.Additionally, the words “herein,” “above,” “below,” and words of similarimport, when used in this application, refer to this application as awhole and not to any particular portions of this application. Where thecontext permits, words using the singular or plural number may alsoinclude the plural or singular number respectively. The word “or” inreference to a list of two or more items, covers all of the followinginterpretations of the word: any one of the items in the list, all ofthe items in the list, and any combination of the items in the list.Likewise the term “and/or” in reference to a list of two or more items,covers all of the following interpretations of the word: any one of theitems in the list, all of the items in the list, and any combination ofthe items in the list.

In some embodiments, certain operations, acts, events, or functions ofany of the algorithms described herein can be performed in a differentsequence, can be added, merged, or left out altogether (e.g., not allare necessary for the practice of the algorithms). In certainembodiments, operations, acts, functions, or events can be performedconcurrently, e.g., through multi-threaded processing, interruptprocessing, or multiple processors or processor cores or on otherparallel architectures, rather than sequentially.

Systems and modules described herein may comprise software, firmware,hardware, or any combination(s) of software, firmware, or hardwaresuitable for the purposes described. Software and other modules mayreside and execute on servers, workstations, personal computers,computerized tablets, PDAs, and other computing devices suitable for thepurposes described herein. Software and other modules may be accessiblevia local computer memory, via a network, via a browser, or via othermeans suitable for the purposes described herein. Data structuresdescribed herein may comprise computer files, variables, programmingarrays, programming structures, or any electronic information storageschemes or methods, or any combinations thereof, suitable for thepurposes described herein. User interface elements described herein maycomprise elements from graphical user interfaces, interactive voiceresponse, command line interfaces, and other suitable interfaces.

Further, processing of the various components of the illustrated systemscan be distributed across multiple machines, networks, and othercomputing resources. Two or more components of a system can be combinedinto fewer components. Various components of the illustrated systems canbe implemented in one or more virtual machines, rather than in dedicatedcomputer hardware systems and/or computing devices. Likewise, the datarepositories shown can represent physical and/or logical data storage,including, e.g., storage area networks or other distributed storagesystems. Moreover, in some embodiments the connections between thecomponents shown represent possible paths of data flow, rather thanactual connections between hardware. While some examples of possibleconnections are shown, any of the subset of the components shown cancommunicate with any other subset of components in variousimplementations.

Embodiments are also described above with reference to flow chartillustrations and/or block diagrams of methods, apparatus (systems) andcomputer program products. Each block of the flow chart illustrationsand/or block diagrams, and combinations of blocks in the flow chartillustrations and/or block diagrams, may be implemented by computerprogram instructions. Such instructions may be provided to a processorof a general purpose computer, special purpose computer,specially-equipped computer (e.g., comprising a high-performancedatabase server, a graphics subsystem, etc.) or other programmable dataprocessing apparatus to produce a machine, such that the instructions,which execute via the processor(s) of the computer or other programmabledata processing apparatus, create means for implementing the actsspecified in the flow chart and/or block diagram block or blocks. Thesecomputer program instructions may also be stored in a non-transitorycomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to operate in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instruction meanswhich implement the acts specified in the flow chart and/or blockdiagram block or blocks. The computer program instructions may also beloaded to a computing device or other programmable data processingapparatus to cause operations to be performed on the computing device orother programmable apparatus to produce a computer implemented processsuch that the instructions which execute on the computing device orother programmable apparatus provide steps for implementing the actsspecified in the flow chart and/or block diagram block or blocks.

Any patents and applications and other references noted above, includingany that may be listed in accompanying filing papers, are incorporatedherein by reference. Aspects of the invention can be modified, ifnecessary, to employ the systems, functions, and concepts of the variousreferences described above to provide yet further implementations of theinvention. These and other changes can be made to the invention in lightof the above Detailed Description. While the above description describescertain examples of the invention, and describes the best modecontemplated, no matter how detailed the above appears in text, theinvention can be practiced in many ways. Details of the system may varyconsiderably in its specific implementation, while still beingencompassed by the invention disclosed herein. As noted above,particular terminology used when describing certain features or aspectsof the invention should not be taken to imply that the terminology isbeing redefined herein to be restricted to any specific characteristics,features, or aspects of the invention with which that terminology isassociated. In general, the terms used in the following claims shouldnot be construed to limit the invention to the specific examplesdisclosed in the specification, unless the above Detailed Descriptionsection explicitly defines such terms. Accordingly, the actual scope ofthe invention encompasses not only the disclosed examples, but also allequivalent ways of practicing or implementing the invention under theclaims.

To reduce the number of claims, certain aspects of the invention arepresented below in certain claim forms, but the applicant contemplatesother aspects of the invention in any number of claim forms. Forexample, while only one aspect of the invention is recited as ameans-plus-function claim under 35 U.S.C sec. 112(f) (AIA), otheraspects may likewise be embodied as a means-plus-function claim, or inother forms, such as being embodied in a computer-readable medium. Anyclaims intended to be treated under 35 U.S.C. § 112(f) will begin withthe words “means for,” but use of the term “for” in any other context isnot intended to invoke treatment under 35 U.S.C. § 112(f). Accordingly,the applicant reserves the right to pursue additional claims afterfiling this application, in either this application or in a continuingapplication.

What is claimed is:
 1. A computer-implemented method comprising: backingup primary data into one or more secondary copies to be stored at adeduplication appliance that comprises one or more data storage devicesand wherein the deduplication appliance is capable of performingdeduplication; wherein the backing up comprises: by a first computingdevice, generating without deduplication a first data stream transmittedto the deduplication appliance, wherein the first data stream comprisesfirst data chunks and does not comprise second data chunks and thirddata chunks, wherein each first data chunk comprises payload data fromthe primary data being backed up, and wherein the first computing devicecomprises one or more processors and computer memory; by the firstcomputing device, generating without deduplication a second data streamtransmitted to the deduplication appliance, wherein the second datastream comprises the second data chunks and does not comprise the firstdata chunks and the third data chunks, wherein each second data chunkcomprises metadata for the primary data being backed up and furtherwherein each second data chunk points to one or more first data chunksof the first data stream; by the first computing device, generatingwithout deduplication a third data stream transmitted to thededuplication appliance, wherein the third data stream comprises thethird data chunks and does not comprise the first data chunks and thesecond data chunks, wherein each third data chunk points to acorresponding second data chunk of the second data stream; and by thefirst computing device, instructing the deduplication appliance: toapply deduplication to the first data chunks of the first data stream,which results in deduplicated first data chunks, to store thededuplicated first data chunks at the deduplication appliance, to storethe second data chunks of the second data stream at the deduplicationappliance without applying deduplication thereto, and to store the thirddata chunks of the third data stream at the deduplication appliancewithout applying deduplication thereto.
 2. The method of claim 1 furthercomprising: by the first computing device, storing in an associatedindex contents of the third data chunks which point to the correspondingsecond data chunks of the second data stream.
 3. The method of claim 1,further comprising: by the first computing device, storing in an index,which is associated with the first computing device, contents of thethird data chunks which point to the corresponding second data chunks ofthe second data stream, wherein the first computing device adds to theindex the metadata for the primary data from the second data chunks. 4.The method of claim 1, wherein the first computing device is configuredto transmit the first data stream, the second data stream, and the thirddata stream without deduplication to the deduplication appliance.
 5. Themethod of claim 1, wherein a given second data chunk includes an offsetof a corresponding first data chunk within the first data stream.
 6. Themethod of claim 1, wherein a given third data chunk includes an offsetof the corresponding second data chunk within the second data stream. 7.The method of claim 1, wherein the first computing device executes amedia agent that generates the first data stream, the second datastream, and the third data stream, and also executes a data agent thataccesses the primary data being backed up; and wherein the firstcomputing device processes the primary data being backed up fordeduplication by and storage at the deduplication appliance as the oneor more secondary copies.
 8. The method of claim 1 further comprising:in response to instructions to restore a first secondary copy from thededuplication appliance: by the first computing device, extracting froman associated index, information about the first secondary copy, whereinthe information comprises pointers to a second data chunk stored withoutdeduplication at the deduplication appliance, wherein the second datachunk comprises metadata for the first secondary copy and furthercomprises one or more pointers to corresponding one or more first datachunks stored with deduplication at the deduplication appliance, andwherein a given first data chunk comprises payload data of the firstsecondary copy; by the first computing device, causing the deduplicationappliance to transmit to the first computing device a fourth data streamthat comprises the second data chunk; by the first computing device,causing the deduplication appliance to transmit to the first computingdevice a fifth data stream that comprises the one or more first datachunks pointed to by the one or more pointers of the second data chunk,wherein the deduplication appliance rehydrates at least some of thefirst data chunks before transmitting the fifth data stream to the firstcomputing device; and by the first computing device processing the firstdata chunks and the metadata in the second data chunk to generate asixth data stream that restores the first secondary copy into primarydata.
 9. The method of claim 1 further comprising: in response toinstructions to restore a first secondary copy from the deduplicationappliance: by the first computing device, extracting from an associatedindex a second data chunk, wherein the second data chunk comprisesmetadata for the first secondary copy and further comprises one or morepointers to corresponding one or more first data chunks stored withdeduplication at the deduplication appliance, and wherein a given firstdata chunk comprises payload data of the first secondary copy; by thefirst computing device, causing the deduplication appliance to transmitto the first computing device a fourth data stream that comprises theone or more first data chunks pointed to by the one or more pointers ofthe second data chunk, wherein at least some of the first data chunksare rehydrated by the deduplication appliance before transmitting thefourth data stream to the first computing device; and by the firstcomputing device processing the first data chunks and the metadata inthe second data chunk to generate a sixth data stream that restores thefirst secondary copy into primary data.
 10. The method of claim 1,wherein a storage manager instructs the first computing device toprocess the primary data being backed up for further processing by andstorage at the deduplication appliance as the one or more secondarycopies, and wherein the storage manager executes on one of: the firstcomputing device and a second computing device distinct from the firstcomputing device.
 11. A system comprising: a first computing devicecomprising one or more hardware processors and computer memory; whereinthe first computing device is programmed to: generate withoutdeduplication a first data stream transmitted to a deduplicationappliance, wherein the deduplication appliance comprises one or moredata storage devices and is capable of performing deduplication, whereinthe first data stream comprises first data chunks and does not comprisesecond data chunks and third data chunks, wherein each first data chunkcomprises payload data from primary data being backed up into one ormore secondary copies that are to be stored at the deduplicationappliance; generate without deduplication a second data streamtransmitted to the deduplication appliance, wherein the second datastream comprises the second data chunks and does not comprise the firstdata chunks and the third data chunks, wherein each second data chunkcomprises metadata for the primary data being backed up and furtherwherein each second data chunk points to one or more first data chunksof the first data stream; generate without deduplication a third datastream transmitted to the deduplication appliance, wherein the thirddata stream comprises the third data chunks and does not comprise thefirst data chunks and the second data chunks, wherein each third datachunk points to a corresponding second data chunk of the second datastream; and instruct the deduplication appliance: to apply deduplicationto the first data chunks of the first data stream, which results indeduplicated first data chunks, to store the deduplicated first datachunks at the deduplication appliance, to store the second data chunksof the second data stream at the deduplication appliance withoutapplying deduplication thereto, and to store the third data chunks ofthe third data stream at the deduplication appliance without applyingdeduplication thereto.
 12. The system of claim 11, wherein the firstcomputing device is further programmed to store, in an associated index,contents of the third data chunks which point to the correspondingsecond data chunks of the second data stream.
 13. The system of claim11, wherein the first computing device is further programmed to: store,in an index, which is associated with the first computing device,contents of the third data chunks, wherein the contents point to thecorresponding second data chunks of the second data stream; and add tothe index the metadata for the primary data from the second data chunks.14. The system of claim 11, wherein a given second data chunk includesan offset of a corresponding first data chunk within the first datastream, and wherein a given third data chunk includes an offset of thecorresponding second data chunk within the second data stream.
 15. Thesystem of claim 11, wherein the first computing device is furtherprogrammed to: execute a media agent that generates the first datastream, the second data stream, and the third data stream, execute adata agent that accesses the primary data being backed up, and processthe primary data being backed up for deduplication by, and for storageat, the deduplication appliance as the one or more secondary copies. 16.The system of claim 11, wherein the first computing device is furtherprogrammed to: in response to instructions to restore a first secondarycopy from the deduplication appliance: extract from an associated indexa second data chunk, which comprises metadata for the first secondarycopy and further comprises one or more pointers to corresponding one ormore first data chunks stored with deduplication at the deduplicationappliance, and wherein a given first data chunk comprises payload dataof the first secondary copy; cause the deduplication appliance totransmit to the first computing device a fourth data stream thatcomprises the one or more first data chunks pointed to by the one ormore pointers in the second data chunk, wherein at least some of thefirst data chunks are rehydrated by the deduplication appliance beforetransmitting the fourth data stream to the first computing device; andprocess the first data chunks and the metadata in the second data chunkto generate a sixth data stream that restores the first secondary copyinto primary data.
 17. A computer-implemented method comprising: by afirst computing device comprising one or more hardware processors andcomputer memory, receiving instructions to generate an auxiliary copythat is based on a secondary copy that is stored in a deduplicationappliance, wherein the deduplication appliance is distinct from and incommunication with the first computing device, and wherein thededuplication appliance comprises one or more data storage devices andis capable of self-managed deduplication; and responsive to theinstructions to generate the auxiliary copy: accessing an index thatcomprises index data chunks, wherein each index data chunk points to acorresponding metadata chunk previously transmitted by the firstcomputing device to the deduplication appliance when the secondary copywas initially created, wherein each metadata chunk comprises metadataabout the secondary copy and one or more pointers to corresponding oneor more payload data chunks of the secondary copy previously transmittedby the first computing device to the deduplication appliance when thesecondary copy was initially created, and wherein each payload datachunk is stored with deduplication at the deduplication appliance andcomprises payload data of the secondary copy; based on the index,determining a first set of index data chunks corresponding to thesecondary copy; transmitting the first set of index data chunkscorresponding to the secondary copy to the deduplication appliance; andinstructing the deduplication appliance to generate the auxiliary copybased on (i) a set of metadata chunks at the deduplication appliancethat are pointed to by the first set of index data chunks, and furtherbased on (ii) a set of payload data chunks at the deduplicationappliance that are pointed to by the set of metadata chunks, wherein togenerate the auxiliary copy, the first computing device does nottransmit the set of payload data chunks to the deduplication appliance;and wherein the auxiliary copy is generated by the deduplicationappliance, based on the set of metadata chunks and the set of payloaddata chunks that are stored at the deduplication appliance.
 18. Themethod of claim 17, wherein the index further comprises the set ofmetadata chunks.
 19. The method of claim 17, wherein the index furthercomprises the set of metadata chunks, and further comprising: furtherbased on the index, determining the set of metadata chunks pointed to bythe first set of index data chunks; generating a second data streamtransmitted to the deduplication appliance, wherein the second datastream comprises the set of metadata chunks.
 20. The method of claim 17,further comprising: based on the index, generating a second data streamtransmitted to a second deduplication appliance, which is distinct fromthe deduplication appliance, wherein the second data stream comprisesthe first set of index data chunks corresponding to the secondary copy;instructing the second deduplication appliance to generate and store asecond auxiliary copy based on: (a) the set of metadata chunks, whichare stored at the deduplication appliance and are pointed to by thefirst set of index data chunks and further based on (b) the set ofpayload data chunks pointed to by the set of metadata chunks and whichare also stored at the deduplication appliance, wherein to generate thesecond auxiliary copy, the first computing device does not transmit theset of payload data chunks to either one of the deduplication applianceand the second deduplication appliance; and wherein the second auxiliarycopy is generated by the second deduplication appliance, and wherein thesecond deduplication appliance obtains the set of metadata chunks andthe set of payload data chunks for the second auxiliary copy from thededuplication appliance.